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/audit-security)<a href="https://agentmods.dev/commands/kumaran-is/claude-code-onboarding/audit-security"><img src="https://agentmods.dev/badge/commands/kumaran-is/claude-code-onboarding/audit-security/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/kumaran-is/claude-code-onboarding/audit-security"><img src="https://agentmods.dev/badge/commands/kumaran-is/claude-code-onboarding/audit-security.svg" alt="Reviewed on agentmods" width="80" 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.00026 | $0.01781 |
| Opus 5.5 | $0.00010 | $0.00712 |
| Sonnet 5.5 | $0.00005 | $0.00356 |
| Haiku 4.5 | $0.00003 | $0.00178 |
Grade A, and why
audit-security 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 1mo 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Audit
Run a comprehensive security audit on the codebase.
Process
-
Determine scope — audit
$ARGUMENTSif provided, otherwise audit the full project -
Delegate to
security-revieweragent with the following checks:- Hardcoded secrets, API keys, tokens, passwords
- OWASP Top 10 vulnerabilities (injection, XSS, SSRF, broken auth, etc.)
- Unsafe deserialization or eval usage
- Missing input validation at system boundaries
- Insecure cryptographic practices
- Exposed debug endpoints or verbose error messages in production
-
Check configuration files:
.envfiles not in.gitignore- Secrets in
docker-compose.ymlor CI config - Overly permissive CORS or security headers
-
Check dependencies (if applicable):
- Run
npm auditfor Node.js projects - Run
pip auditfor Python projects - Flag known CVEs in
pom.xmldependencies
- Run
-
Dependency vulnerability scan (deep scan):
Run the dependency scanner for a comprehensive CVE analysis with priority scoring:
/security-dependencies $ARGUMENTSInclude the top 5 highest-priority CVEs (by priority score) in the final report. Flag any CVSS 9+ findings as blocking -- do not approve the release until resolved.
-
Agentic CI/CD audit (if
.github/workflows/directory exists):Load skill:
claude-actions-auditorGlob
.github/workflows/*.ymland.github/workflows/*.yaml. If any workflow file containsanthropics/claude-code-action, run the full 5-step audit from theclaude-actions-auditorskill.Add findings to the final report under a new section:
### Agentic CI/CD - [workflow-file:line] [vector name] [description]If no workflows or no Claude Code Action steps found: note "No Claude Code Action workflows detected — agentic CI/CD audit skipped."
-
Compute 007 Security Score (run after all findings are collected from steps 2–6):
Calculate a 0–100 weighted score across 8 domains. For each domain, start at 100 and apply deductions:
- CRITICAL finding in domain: −15 pts
- HIGH finding in domain: −8 pts
- MEDIUM finding in domain: −3 pts
- LOW finding in domain: −1 pt
- Floor at 0 per domain
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.
- 1mo ago First seen · 184 lines · 26 tokens per session scan A c50fef72bf8e
audit-security is a command published in the GitHub repository kumaran-is/claude-code-onboarding (36 stars, last pushed 3mo ago), licensed MIT. It adds 26 tokens to every session and 1,781 once invoked, about $0.0001 per session on Opus 5.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
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.
react-native
Command "react-native" from getsentry/toolkit, covering examples, also associate with a release and distribution(s), xcode build step (react-native xcode) and important notes.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.