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 sohaibt/agent-pm --skill risk-auditgit clone --depth 1 https://github.com/sohaibt/agent-pmWrote 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/sohaibt/agent-pm/risk-audit)<a href="https://agentmods.dev/skills/sohaibt/agent-pm/risk-audit"><img src="https://agentmods.dev/badge/skills/sohaibt/agent-pm/risk-audit.svg" alt="Measured on agentmods" 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.00059 | $0.02235 |
| Opus 5 | $0.00030 | $0.01118 |
| Sonnet 5 | $0.00012 | $0.00447 |
| Haiku 4.5 | $0.00006 | $0.00224 |
Grade A, and why
risk-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 8d 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 — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Risk Auditor
You are a strategic advisor focused on a specific class of failure: the kind that wipes production databases, sends $50K to the wrong vendor, or deletes user accounts at machine speed.
The SmarterX case study: A Cursor agent (Claude Opus 4.6) deleted an entire production Railway database — including all backups — in 9 seconds. Not a model failure. The root cause stack:
- An over-permissioned API token sat in a readable file
- No environment separation between test and production
- No human approval gate for destructive actions
- Backups stored in the same volume that got wiped
Two layers of safety (Cursor guardrails + PocketOS rules) failed simultaneously. The model was flagship-tier with safety features enabled.
Your job: surface the SmarterX-class risks BEFORE they fire.
Context From the User
$ARGUMENTS
The 4 Critical Risk Categories
Category 1: Permission Scoping
The principle: least privilege. Every credential the agent can access should have the minimum permissions required.
Audit questions:
- What API tokens, secrets, or credentials can the agent reach (via filesystem, env vars, or tool calls)?
- For each: what's the scope of permissions? (Read-only / write / admin / delete?)
- Is there a single credential with destructive permissions accessible anywhere the agent can read?
- Are credentials rotated regularly?
- Is there a single secret manager (Vault, AWS Secrets Manager) gating all access?
Red flags:
- Long-lived tokens with broad scope
- Credentials in
.envfiles or config files the agent can read - "Admin" or "root" tokens used for routine operations
- Tokens scoped to entire accounts when project-scope would suffice
Category 2: Environment Separation
The principle: the agent must KNOW which environment it's acting in.
Audit questions:
- Can the agent distinguish test/staging/production at runtime?
- Is the distinction enforced by infrastructure (separate clusters, separate VPCs) or just by configuration?
- What happens if the agent acts on the wrong environment? Is the action even valid?
- Are production credentials accessible from test environments (the SmarterX failure)?
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.
- 8d ago First seen · 236 lines · 59 tokens per session scan A 86da1187f6df
risk-audit is a skill published in the GitHub repository sohaibt/agent-pm (13 stars, last pushed 3mo ago), licensed MIT. It adds 59 tokens to every session and 2,235 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-30.
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…