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/solid-fixnpx skills add muthuspark/solid-audit --skill solid-fixgit 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.00020 | $0.01397 |
| Opus 5 | $0.00010 | $0.00698 |
| Sonnet 5 | $0.00004 | $0.00279 |
| Haiku 4.5 | $0.00002 | $0.00140 |
Grade A, and why
solid-fix 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 — 121 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 /solid-fix (optionally with a file path argument, e.g. /solid-fix src/services/order.py).
Scope Detection
Determine which files to analyze using this priority order:
- Argument — If the user provided a file or directory path after
/solid-fix, 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
Orchestration Logic
Run all five SOLID principle analyses sequentially in this order: S → O → L → I → D
This order is deliberate:
- SRP extraction changes the class structure that OCP/DIP fixes might also target
- Running S first ensures the class boundaries are stable before open/closed or injection fixes are proposed
Step 1 — Collect All Violations
For each principle in order, analyze the scoped files:
S — Single Responsibility: Classes/functions with multiple unrelated concerns
O — Open/Closed: Switch-on-type chains, isinstance dispatch, direct subclass instantiation by condition
L — Liskov Substitution: raise NotImplementedError in overrides, narrowed preconditions, strengthened postconditions
I — Interface Segregation: Fat ABCs/interfaces where implementors stub ≥ half the methods
D — Dependency Inversion: Concrete class instantiation in constructors, no abstraction layer
Group all violations by principle. A violation flagged as unsafe (safe_to_fix = false) during analysis is kept in the report but marked as skipped.
Step 2 — Present Grouped Confirmation Prompt
Present one single confirmation prompt listing all violations grouped by principle:
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 · 121 lines · 20 tokens per session scan A a963e2b5de02
solid-fix is a skill published in the GitHub repository muthuspark/solid-audit (5 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 20 tokens to every session and 1,397 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.