Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/binaryhb0916/isparto/security-ispartogit clone --depth 1 https://github.com/BinaryHB0916/iSpartoWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.00580 |
| Opus 5 | $0.00000 | $0.00290 |
| Sonnet 5 | $0.00000 | $0.00116 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
security-isparto scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
You are the Team Lead. The user has run /security-isparto to perform a milestone-level full security audit.
IMPORTANT: Detect the user's language and respond in that same language (Chinese or English only).
Your responsibility: Execute a comprehensive security scan of the entire project, covering code content, file patterns, .gitignore completeness, git history, and dependency safety.
-
Full file content scan:
- Read
~/.isparto/hooks/process-observer/rules/security-patterns.json - Scan ALL project files (not just staged) against all patterns in secrets, pii, and sensitive_files sections
- Respect
.secureignorewhitelist if present - Report findings grouped by severity: critical → high → warning
- Read
-
.gitignore completeness check:
- Compare the project's .gitignore against the
gitignore_baseline.requiredarray in security-patterns.json - List any missing entries and suggest additions
- Check if any gitignored file patterns have been force-added with
git add -f(rungit ls-files -i --exclude-standard)
- Compare the project's .gitignore against the
-
Git history check:
- Run
git log -p --all -G 'AKIA|sk-ant-|sk-proj-|BEGIN PRIVATE KEY|sk_test_|sk_live_|ghp_|gho_' -- . ':(exclude)*.md'to find commits that introduced or removed secrets - Note: uses
-Gwith regex OR (not multiple-Sflags, which are AND) - If historical leaks found: recommend git filter-repo or BFG Repo-Cleaner, and emphasize that ALL leaked credentials must be rotated immediately
- Run
-
Dependency security check (adapt to project tech stack):
- Node.js: run
npm auditif package-lock.json exists - Python: suggest
pip-auditorsafety checkif requirements.txt exists - iOS: check Podfile.lock for known vulnerable pod versions
- General: look for suspiciously-named dependencies (typosquatting patterns — common names with character substitution)
- Node.js: run
-
Output audit report in this format:
=== Security Audit Report === Scan time: [timestamp] Project: [project name] Branch: [current branch] --- Critical --- [findings or "None"] --- High --- [findings or "None"] --- Warning --- [findings or "None"] --- .gitignore Check --- [missing entries or "Complete"] --- Git History --- [historical leaks or "Clean"] --- Dependency Security --- [vulnerabilities or "No known vulnerabilities found"] --- Summary --- [PASS / NEEDS ATTENTION: N issues to resolve]
$ARGUMENTS
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 59 lines · 0 tokens per session scan A 24b752456707
security-isparto is a command published in the GitHub repository BinaryHB0916/iSparto (59 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 580 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
pr-address
Address PR review comments on current branch.
enforce_standards
CRITICAL: Before running the code standards enforcer, we must prepare the stack properly and abort if there are merge conflicts.
validate_changed_docstrings
Validates Python docstrings in all uncommitted changed files using Sphinx parsing.
OPSX: Continue
Continue working on a change - create the next artifact (Experimental).
OPSX: Propose
Propose a new change - create it and generate all artifacts in one step.
spec-research
需求 → 约束集(并行探索 + OPSX 提案).