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.
git clone --depth 1 https://github.com/kumaran-is/claude-code-onboardingWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/kumaran-is/claude-code-onboarding/security-sast)<a href="https://agentmods.dev/commands/kumaran-is/claude-code-onboarding/security-sast"><img src="https://agentmods.dev/badge/commands/kumaran-is/claude-code-onboarding/security-sast.svg" alt="Measured on agentmods" height="20"></a>What 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.1 | $0.00053 | $0.00702 |
| Opus 5 | $0.00026 | $0.00351 |
| Sonnet 5 | $0.00011 | $0.00140 |
| Haiku 4.5 | $0.00005 | $0.00070 |
Grade A, and why
security-sast 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAST Security Scan
Run static application security testing on the specified path.
Scan Path
Scan $ARGUMENTS if provided, otherwise scan the current directory.
SCAN_PATH="${ARGUMENTS:-.}"
Step 1: Language Detection
Detect which ecosystems are present in the scan path:
[ -f pom.xml ] && echo "Java/Spring detected"
[ -f package.json ] && echo "TypeScript/Node detected"
[ -f pyproject.toml ] || [ -f requirements.txt ] && echo "Python detected"
[ -f pubspec.yaml ] && echo "Dart/Flutter detected"
Step 2: Run Language-Specific Scanners
Java (if pom.xml found)
mvn verify -Pspotbugs -DskipTests 2>&1 | grep -E "BUG|WARNING|ERROR"
semgrep --config=p/java --json ${SCAN_PATH} 2>/dev/null
TypeScript/NestJS/Angular (if package.json found)
npx eslint --plugin security --ext .ts ${SCAN_PATH} 2>&1 | grep -E "error|warning" | head -50
semgrep --config=p/typescript --json ${SCAN_PATH} 2>/dev/null
Python (if pyproject.toml or requirements.txt found)
bandit -r ${SCAN_PATH} -f json -ll 2>/dev/null
semgrep --config=p/python --json ${SCAN_PATH} 2>/dev/null
Dart/Flutter (if pubspec.yaml found)
dart analyze ${SCAN_PATH} 2>&1
flutter analyze ${SCAN_PATH} 2>&1 | grep -E "error|warning|info"
All Languages (if .semgrep.yml exists)
semgrep --config=.semgrep.yml --json ${SCAN_PATH} 2>/dev/null
Step 3: Risk Score Calculation
Risk Score = min(100, sum of:
CRITICAL findings x 10
HIGH findings x 7
MEDIUM findings x 4
LOW findings x 1
)
Step 4: Output
SAST SCAN RESULTS
=================
Path: [scanned path]
Languages: [detected languages]
Risk Score: [0-100]
CRITICAL ([count]):
- [file:line] [finding description] [CWE]
HIGH ([count]):
- [file:line] [finding description] [CWE]
MEDIUM ([count]):
- [file:line] [finding description] [CWE]
LOW ([count]):
- [finding description]
NEXT STEPS:
[ ] Fix all CRITICAL findings before merge
[ ] Review HIGH findings — fix or document accepted risk
[ ] Run /security-hardening for comprehensive remediation
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.
- 5d ago First seen · 105 lines · 53 tokens per session scan A f9a6316d29d4
security-sast is a command published in the GitHub repository kumaran-is/claude-code-onboarding (35 stars, last pushed 2mo ago), licensed MIT. It adds 53 tokens to every session and 702 once invoked, about $0.0003 per session on Opus 5. 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-09-03.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.