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 Justinmendezai/The-Adam-Repo --skill security-auditgit clone --depth 1 https://github.com/Justinmendezai/The-Adam-RepoWrote 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/justinmendezai/the-adam-repo/security-audit)<a href="https://agentmods.dev/skills/justinmendezai/the-adam-repo/security-audit"><img src="https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/security-audit/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/justinmendezai/the-adam-repo/security-audit"><img src="https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/security-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00062 | $0.01335 |
| Opus 5 | $0.00031 | $0.00668 |
| Sonnet 5 | $0.00012 | $0.00267 |
| Haiku 4.5 | $0.00006 | $0.00134 |
Grade A, and why
security-audit 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 12d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
security-audit
Produces durable audit artifacts other agents consume for refactor planning and security test design. No product code changes unless the human explicitly asks for remediation in the same session.
When to use
- Before a security refactor sprint (ecosystem or single service).
- After major auth/routing changes — refresh the audit.
- When
packet/PACKET.mdreferencessecurity.audit_refand the file is stale or missing. - Human asks for “security audit”, “threat inventory”, or “what’s exposed”.
Pair with security-acceptance after fixes land.
Outputs (required)
Write under scratch/security-audit/ at the project root being audited (for ecosystem audits, prefer ~/adam/scratch/<name>/ or a dedicated meta repo):
| File | Purpose |
|---|---|
audit-<YYYYMMDD>.json |
Machine-readable; validate against schemas/security-audit.schema.json |
audit-<YYYYMMDD>.md |
Human-readable inventory + top findings per repo |
planning-brief.md |
For downstream agents: P0–P2 priorities, suggested vertical slices, suggested test types — no implementation |
Update agent-control/security-status.md when the target repo has agent-control/ (summary table + link to audit files). Subagents: read-only on agent-control/.
Workflow
1. Define scope
- Ecosystem: list absolute paths and repo ids (e.g.
api-service,web-app). - Single repo:
tech_context.repo_pathfrom packet or user path. - Read
packet/PACKET.mdsecurityblock if present (in_scope_services,threat_model_ref,audit_ref).
2. Per-repo inventory (read-only)
For each repo, document:
- Stack — language, framework, how it runs, bind address.
- Auth model — route classes: public, session, Bearer, HMAC, webhook signatures; note “fail open if secret empty” patterns.
- Secrets —
.env.examplefields; grep forapi_key,secret,password,token,bearer,sk-,AKIAin source (report paths, never paste live values). - HTTP surface — API routes, CORS, uploads, admin/ops routes.
- Data stores — DB, object storage, external APIs.
- Docker/infra — compose ports, default creds.
- Existing security tests — auth tests, HMAC tests, bandit/semgrep/npm audit scripts.
- CI —
.github/workflowssecurity steps.
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.
- 12d ago First seen · 129 lines · 62 tokens per session scan A 47859d1571c0
security-audit is a skill published in the GitHub repository Justinmendezai/The-Adam-Repo (12 stars, last pushed 18d ago), licensed Apache-2.0. It adds 62 tokens to every session and 1,335 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…