agentmods.dev

auditing-security

auditing-security is a skill for Claude Code, Codex from porcupine-md/jonggrang. It costs 16 tokens per session (441 once invoked), scanned A, original, MIT.

A read-only security review of an application’s infrastructure, code settings, secrets, and dependencies. It uses OWASP checks and STRIDE, a method for thinking through common threat types.

In plain words
What is it for?
Use it to inspect a feature’s files, check security risks with available audit tools, and save a security report in the feature directory.
Why use it?
It helps find exposed secrets, unsafe settings, weak input checks, and risky dependencies without changing application code.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 16repo 1mo ago A scan 16 tokens original MIT

Good fit Use it to inspect a feature’s files, check security risks with available audit tools, and save a security report in the feature directory.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/porcupine-md/jonggrang/auditing-security
View source ↗ porcupine-md/jonggrang jonggrang.dev
Install

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.

Any agent
npx skills add porcupine-md/jonggrang --skill auditing-security
Clone the repo
git clone --depth 1 https://github.com/porcupine-md/jonggrang

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for auditing-security

README.md
[![agentmods](https://agentmods.dev/badge/skills/porcupine-md/jonggrang/auditing-security/github.svg)](https://agentmods.dev/skills/porcupine-md/jonggrang/auditing-security)
Your own site
<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.

agentmods 80×15 button for auditing-security

Your own site · 80×15
<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>
Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 441 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00016 $0.00441
Opus 5.5 $0.00006 $0.00176
Sonnet 5.5 $0.00003 $0.00088
Haiku 4.5 $0.00002 $0.00044

Measured 1mo ago against content hash 6e64362ad44b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

skills/library/security/auditing-security/SKILL.md · 36 lines

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

  1. Information Gathering (READ-ONLY):
    • Use glob to find target application files relevant to the feature.
    • Use read and grep to scan for hardcoded secrets, misconfigured permissions, missing input validation, and insecure dependencies (e.g., check package.json, .env.example).
    • Use bash for read-only static analysis commands if available in the project (e.g., npm audit, pip-audit). DO NOT execute code that modifies the workspace.
  2. 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.
  3. 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).
  4. Save Report:
    • Write the final report using the write tool to .jonggrang/.output/features/<active-feature-dir>/security-audit.md.

Completion Signal

When the audit report is successfully saved, output exactly:

SECURITY_AUDIT_COMPLETE

Changes

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.

  1. 1mo ago First seen · 36 lines · 16 tokens per session scan A 6e64362ad44b

Subscribe to this mod's changes

auditing-security is a skill published in the GitHub repository porcupine-md/jonggrang (16 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 441 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-08-30.

Code reviewSecurity
Related

Other skills, from other repositories

autoreview

Structured code review through the shared OpenClaw agent-skills installation.

openclaw/clawhub · 17 tokens

omh-code-review

This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

rlaope/oh-my-hermes · 48 tokens

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"…

umputun/revdiff · 84 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens

explore-unknowns

Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…

dzhng/skills · 162 tokens

asplos-writing-style

Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…

brycewang-stanford/Awesome-Journal-Skills · 65 tokens