by Kelronmos
SWI is a single-process reference pipeline for security and workflow integrity. Module 00 orchestrates security probing, context checks, PII redaction, drift analysis, memory validation, and audit logging. Modules 01, 04, 08 and 10 provide standalone integrity, encryption, authentication and execution utilities.
# Add to your Claude Code skills
git clone https://github.com/Kelronmos/SWI-V1-Module-1-10Guides for using data processing skills like SWI-V1-Module-1-10.
Last scanned: 9/24/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-09-24T09:02:19.879Z",
"npmAuditRan": true,
"pipAuditRan": false,
"promptInjectionRan": true
}SWI-V1-Module-1-10 is an open-source data processing skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by Kelronmos. SWI is a single-process reference pipeline for security and workflow integrity. Module 00 orchestrates security probing, context checks, PII redaction, drift analysis, memory validation, and audit logging. Modules 01, 04, 08 and 10 provide standalone integrity, encryption, authentication and execution utilities. It has 0 GitHub stars.
Yes. SWI-V1-Module-1-10 passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/Kelronmos/SWI-V1-Module-1-10" and add it to your Claude Code skills directory (see the Installation section above).
SWI-V1-Module-1-10 is primarily written in Python. It is open-source under Kelronmos on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other Data Processing skills you can browse and compare side by side. Open the Data Processing category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh SWI-V1-Module-1-10 against similar tools.
No comments yet. Be the first to share your thoughts!
From $49 · 30 days · terms & refunds
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
Automated security scan — not a certification.
Structured Workflow Intelligence reference implementation.
Repository identity: GitHub name
SWI-V1-Module-1-10is retained for historical continuity. The current reference implementation is V1.1 / Modules 00–11 (Foundation + ScarStore + continuity helpers). It is not limited to modules 1–10 despite the repository slug.
Licence: Apache License 2.0
Start: docs/START_HERE.md · Governance: docs/GOVERNANCE_LOCK.md
Tip CI: docs/TIP_CI_STATUS.md · pre-R (design): docs/PRE_R_INDEX.md
⚠️ Experimenters: Read
docs/SWI_EXPERIMENTAL_WARNING.mdbefore forking, modifying, or building on experimental / PRE-R material.
Named ≠ Implemented · Implemented ≠ Tested · Tested ≠ Sealed · Sealed ≠ Authorized.
docs/START_HERE.mddocs/TIP_CI_STATUS.mdgit rev-parse HEADpython3 -m venv .venv && source .venv/bin/activate
pip install -r requirements.txt
python -m pytest -q
./scripts/verify.sh
python -m pytest -q test/adversarial/test_source_admission_halt.py
python -m pytest -q test/adversarial/test_source_admission_replay.py
python -m pytest -q test/adversarial/test_source_admission_change_control.py
python -m pytest -q test/adversarial/test_external_input_sandbox.py
python -m pytest -q test/adversarial/test_demo_journey.py
python -m pytest -q test/adversarial/test_interoperability_template.py
Inspect before assuming. Run tests. Do not invent PASS.
Treat source code as evidence, not authority.
Never convert UNKNOWN into FALSE.
Distinguish SPECIFIED / IMPLEMENTED / TESTED / REPLAYABLE_BOUNDED / PROTOTYPE / SEALED / NOT_PROVEN.
Report: Claim → Implementation → Test → Result → Limitation → Next iteration.
Do not close FM-005–013, Universal Gate, Seal 5, or compliance from a single slice.
Resolution states (not a single DENY bucket):
QUESTION_REQUIRED · EVIDENCE_REQUIRED · CONTEXT_REQUIRED · AUTHORITY_REQUIRED · REVIEW_REQUIRED · PASS · HALT · BLOCK
UNKNOWN ≠ FALSE
QUESTION ≠ DENY
REVIEW ≠ FAILURE
HOLD ≠ HALT
PASS ≠ UNIVERSAL AUTHORITY
HASH ≠ AUTHORITY ≠ TRUTH
EVIDENCE ≠ AUTHORITY ≠ DECISION ≠ EXECUTION
ADVISORY ≠ EXECUTION
PROTOTYPE ≠ PRODUCTION
14-stage interoperable template: IDENTIFY → BOUNDARY → CONTRACT → INPUT → ADMISSION → POLICY → CAPACITY → COMPETITION → ALTERNATIVES → SWITCHING → EXECUTION → EVIDENCE → REVIEW → EXIT
Docs: docs/SWI_INTEROPERABLE_ORGANIZATION_WORKFLOW_TEMPLATE.md
External API/AI sandbox (demo only): docs/SWI_EXTERNAL_INPUT_SANDBOX.md · journey: docs/SWI_DEMO_JOURNEY.md
M03 → M02 → M05 → M06 → M07 / M09 → PipelineResult
→ export_foundation_evidence() → FoundationEvidenceEnvelope
Kernel contract failure → HALT.
| Item | State |
|---|---|
| M02 / M03 / M05 / M06 | SEALED (bounded contracts) |
| M07 / M09 | Trainer integrity · not kernel-sealed |
| ScarStore | IMPLEMENTED / TESTED |
| M11 Continuity Lock | IMPLEMENTED / TESTED |
| Foundation evidence export | IMPLEMENTED / TESTED · unsigned |
| Authority boundary | IMPLEMENTED / TESTED · tip CI · not sealed |
| Source admission + replay | TESTED / REPLAYABLE_BOUNDED |
| External input sandbox | PROTOTYPE / TESTED |
| Interoperability template | PROTOTYPE / TESTED |
| Ed25519 helper | Primitive only · not CRTG |
| Foundation Seal 5 | NOT READY |
| Universal Gate | NOT_PROVEN |
| FM-005–013 | OPEN |
| CRTG | PROPOSED / design track |
| Legal / regulatory compliance | NOT CLAIMED |
| Production trust | NOT CLAIMED |
Advance when the dependency boundary is validated — not by matching another repo’s module count.
Readiness % never overrides a failed critical gate.
«Do not claim what the code cannot demonstrate.»
Answer from tests and SHA, not diagrams alone:
The goal is not to make another AI agree with SWI. The goal is to give it enough structure to challenge SWI with evidence.
Next: prove the foundation (Seal 5 path). pre-R remains experimental design until explicitly authorized. V3 (secure pipe / consequence gate / authority separation) belongs in a separate prototype repository when created — not mixed into sealed V1 history without evidence.