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 skills add ShaheerKhawaja/ProductionOS --skill security-scangit clone --depth 1 https://github.com/ShaheerKhawaja/ProductionOSWrote 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/skills/shaheerkhawaja/productionos/security-scan)<a href="https://agentmods.dev/skills/shaheerkhawaja/productionos/security-scan"><img src="https://agentmods.dev/badge/skills/shaheerkhawaja/productionos/security-scan/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/skills/shaheerkhawaja/productionos/security-scan"><img src="https://agentmods.dev/badge/skills/shaheerkhawaja/productionos/security-scan.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.00040 | $0.00463 |
| Opus 5 | $0.00020 | $0.00231 |
| Sonnet 5 | $0.00008 | $0.00093 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
security-scan 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 9d 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
ProductionOS Security Scan
Auto-Triggered Checklist
When this skill activates on a security-sensitive file:
- Secret Detection — Scan for hardcoded API keys, tokens, passwords, connection strings
- Input Validation — Verify all user inputs are validated and sanitized
- Auth Checks — Confirm endpoint has proper authentication and authorization
- SQL Injection — Check for parameterized queries (no string concatenation)
- XSS Prevention — Verify output encoding for user-generated content
- CSRF Protection — Confirm CSRF tokens on state-changing operations
- Dependency CVEs — Flag if file imports packages with known vulnerabilities
Red Flags — STOP If You See These
- Hardcoded secrets (API keys, passwords, tokens in source code)
- Missing authentication on new endpoints
- User input passed directly to database queries
- Unsafe HTML rendering without sanitization
- Disabled CSRF protection
- Overly permissive CORS configuration
- Catch-all error handlers that swallow security exceptions
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.
- 9d ago First seen · 58 lines · 40 tokens per session scan A 1ca46e081cd1
security-scan is a skill published in the GitHub repository ShaheerKhawaja/ProductionOS (8 stars, last pushed 4mo ago), licensed MIT. It adds 40 tokens to every session and 463 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
fellowship
Multi-task orchestrator. Coordinates agent teammates (led by Gandalf) running /quest (code) or /scout (research) workflows. Use when you have multiple independent tasks to run in parallel.
quest
Use for multi-file or multi-step changes that need research and a plan — not single-file fixes under 50 lines that follow an existing pattern (see Escape Hatch below). Runs the Research → Plan → Implement → Review lifecycle with a hard gate leaving each of the first three phases and context compaction between them.
retro
Invoke after a fellowship disbands, or when the user explicitly asks for a retrospective. Collects gate history, palantir alerts, and quest metrics to surface patterns and interactively recommend configuration improvements.
lembas
Use between workflow phases or when context feels bloated. Writes a structured checkpoint capturing task, findings, files, state, and next steps, then continues from that summary instead of the full history. Invoke standalone or automatically between quest phases.
scout
Research & analysis workflow. Investigates questions, gathers findings, optionally validates with a fresh subagent. Produces a report — no code, no PRs, no commits. Use standalone or as a fellowship teammate.
council
Invoke when the user runs /council or from /scout. Quest inlines this orientation as its Research step 2 and does not call it. Loads focused, task-relevant context by reading CLAUDE.md, scanning for related files, and producing a structured Session Context block.