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 tjboudreaux/cc-plugin-engineering-excellence --skill eng-security-safetygit clone --depth 1 https://github.com/tjboudreaux/cc-plugin-engineering-excellenceWrote 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/tjboudreaux/cc-plugin-engineering-excellence/eng-security-safety)<a href="https://agentmods.dev/skills/tjboudreaux/cc-plugin-engineering-excellence/eng-security-safety"><img src="https://agentmods.dev/badge/skills/tjboudreaux/cc-plugin-engineering-excellence/eng-security-safety/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/tjboudreaux/cc-plugin-engineering-excellence/eng-security-safety"><img src="https://agentmods.dev/badge/skills/tjboudreaux/cc-plugin-engineering-excellence/eng-security-safety.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.00028 | $0.00421 |
| Opus 5 | $0.00014 | $0.00211 |
| Sonnet 5 | $0.00006 | $0.00084 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
eng-security-safety 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.
What it actually says
Security and Safety Mindset
Intent
- Treat every change as a potential attack surface or failure amplifier.
- Ensure data classification, secret handling, and permission scopes stay compliant.
- Bake safety checks (rate limits, input validation, monitoring) into the design, not after.
Baseline Checklist
- Threat model quickly: Who could abuse this surface? What capabilities do they need? What happens if they succeed?
- Data stewardship: Classify data touched (PII, payments, assets) and enforce encryption, retention, and locality rules.
- Access + identity: Validate authn/authz paths, key rotation, wallet signatures, and privilege escalation barriers.
- Dependency hygiene: Pin versions, verify licenses, review changelogs, and prefer audited libraries/contracts.
- Secrets + config: Never log secrets; store them in the project’s approved secret manager. Guard env var usage.
Workflow
- Enumerate entry points (mobile UI, API, smart contract, admin tools) and list unchecked inputs.
- Define validation layers: schema-level, business-level, and environment-level (e.g., chain ID, platform version).
- Ensure every state change is reversible or compensatable (feature flags, contract pausing, migration guards).
- Instrument detection: structured logs, metrics, or on-chain events that can surface abuse or regressions fast.
- Document explicit “never do” actions (e.g., disable signature checks, bypass paywalls) inside the PR/issue notes.
Verification
- Run the project’s security/static analysis tooling (linters, contract analyzers, mobile scanners) and fix findings.
- Peer review the threat model summary; confirm secrets and keys are absent from diffs/logs.
- Validate abuse cases end-to-end (invalid payloads, replayed signatures, abusive traffic) before shipping.
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 · 31 lines · 28 tokens per session scan A 698e8482c131
eng-security-safety is a skill published in the GitHub repository tjboudreaux/cc-plugin-engineering-excellence (4 stars, last pushed 7mo ago), licensed MIT. It adds 28 tokens to every session and 421 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-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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
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…