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 porcupine-md/jonggrang --skill auditing-securitygit clone --depth 1 https://github.com/porcupine-md/jonggrangWrote 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/porcupine-md/jonggrang/auditing-security)<a href="https://agentmods.dev/skills/porcupine-md/jonggrang/auditing-security"><img src="https://agentmods.dev/badge/skills/porcupine-md/jonggrang/auditing-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/skills/porcupine-md/jonggrang/auditing-security"><img src="https://agentmods.dev/badge/skills/porcupine-md/jonggrang/auditing-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.00016 | $0.00441 |
| Opus 5 | $0.00008 | $0.00220 |
| Sonnet 5 | $0.00003 | $0.00088 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
auditing-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 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
Auditing Security (CSO Mode)
Role Constraints: Reviewer (STRICTLY READ-ONLY for application code). You MAY NOT modify, fix, or write to application source code.
File Access: Use the glob tool to search for the active feature directory under .jonggrang/.output/features/. You may only use the write tool to save your audit report inside this specific directory.
Objective
Act as Chief Security Officer. Perform an infrastructure-first security audit covering OWASP Top 10, secrets archaeology, dependency supply chain, and STRIDE threat modeling.
Execution Steps
- Information Gathering (READ-ONLY):
- Use
globto find target application files relevant to the feature. - Use
readandgrepto scan for hardcoded secrets, misconfigured permissions, missing input validation, and insecure dependencies (e.g., checkpackage.json,.env.example). - Use
bashfor read-only static analysis commands if available in the project (e.g.,npm audit,pip-audit). DO NOT execute code that modifies the workspace.
- Use
- Analysis Dimensions:
- OWASP Top 10: Injection, Broken Auth, Sensitive Data Exposure, etc.
- STRIDE: Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, Elevation of Privilege.
- Supply Chain: Vulnerable packages or risky third-party integrations.
- Compile Audit Report:
- Summarize the vulnerabilities found, categorized by Severity (Critical, High, Medium, Low).
- Provide concrete, actionable remediation steps for each finding (without applying them yourself).
- Save Report:
- Write the final report using the
writetool to.jonggrang/.output/features/<active-feature-dir>/security-audit.md.
- Write the final report using the
Completion Signal
When the audit report is successfully saved, output exactly:
SECURITY_AUDIT_COMPLETE
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 · 36 lines · 16 tokens per session scan A 6e64362ad44b
auditing-security is a skill published in the GitHub repository porcupine-md/jonggrang (11 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 441 once invoked, about $0.0001 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-30.
Other skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…