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 agentmods add skills/muthuspark/solid-audit/srpnpx skills add muthuspark/solid-audit --skill srpgit clone --depth 1 https://github.com/muthuspark/solid-auditWhat 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 | $0.00014 | $0.01258 |
| Opus 5 | $0.00007 | $0.00629 |
| Sonnet 5 | $0.00003 | $0.00252 |
| Haiku 4.5 | $0.00001 | $0.00126 |
Grade A, and why
srp 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 2d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trigger
This skill activates when the user runs /srp (optionally with a file path argument, e.g. /srp src/services/user.py).
Scope Detection
Determine which files to analyze using this priority order:
- Argument — If the user provided a file or directory path after
/srp, use that directly. - Git staged — Run
git diff --cached --name-only. If output is non-empty, use those files. - Git unstaged — Run
git diff --name-only. If output is non-empty, use those files. - Ask user — If no git diff is available, ask for a file or directory path.
Always skip: *.lock, package-lock.json, yarn.lock, pnpm-lock.yaml, Gemfile.lock, composer.lock, **/migrations/**, **/__generated__/**, **/fixtures/**, **/*.min.js
SRP Fix Logic
Detection
A class or function violates SRP when it handles two or more unrelated concerns. Look for:
- A class with method groups belonging to distinct responsibilities (e.g., data parsing AND persistence AND notification in one class)
- A function that validates, persists, and formats output all in one body
- A class whose name contains "And", "Manager", or "Handler" and does multiple unrelated things
- A class that imports from two or more unrelated domains (e.g., imports both
smtpliband database drivers)
Fix Strategy
For classes: Extract each distinct responsibility into its own focused class:
- Identify the distinct responsibility groups within the violating class
- For each group, create a new class with a single, clear name
- Move the relevant methods/logic to the new class
- Update the original class to accept the new classes via constructor injection (if needed) or remove it entirely
- Preserve the original public interface — callers of the original class must not need to change
For functions: Split a multi-concern function into multiple focused functions:
- Identify the distinct steps in the function body (e.g., validate → persist → notify)
- Extract each step into its own named function with a clear, single-purpose name
- Replace the original body with calls to the extracted functions, or remove the monolith and update callers
- Each extracted function should be testable independently
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.
- 2d ago First seen · 118 lines · 14 tokens per session scan A 4ae2156c68e1
srp is a skill published in the GitHub repository muthuspark/solid-audit (5 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 1,258 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.
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…
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…
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…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…