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 pamela-0/safe-fix-mcp --skill skillgit clone --depth 1 https://github.com/pamela-0/safe-fix-mcpWrote 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/pamela-0/safe-fix-mcp/skill)<a href="https://agentmods.dev/skills/pamela-0/safe-fix-mcp/skill"><img src="https://agentmods.dev/badge/skills/pamela-0/safe-fix-mcp/skill/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/pamela-0/safe-fix-mcp/skill"><img src="https://agentmods.dev/badge/skills/pamela-0/safe-fix-mcp/skill.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.00144 | $0.00570 |
| Opus 5.5 | $0.00058 | $0.00228 |
| Sonnet 5.5 | $0.00029 | $0.00114 |
| Haiku 4.5 | $0.00014 | $0.00057 |
Grade A, and why
safe-fix-mcp 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 1mo 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
safe-fix-mcp
Real static-analysis dead-code detection for Python repos — not a guess. vulture + deptry under the hood, wrapped in a safety-gated auto-PR flow.
When to use each tool
Always start with scan_dead_code (read-only, never modifies anything):
- Call it whenever the user wants a dead-code/bloat report, before recommending any deletion.
- Default
min_confidence=60is fine for a first pass; raise it (e.g. 80-90) if the user reports false positives — Pydantic/TypedDict fields and similar dynamic-access patterns commonly show up as false "unused" at low confidence. - Present findings grouped by kind (unused imports vs. unused functions/classes vs. unused dependencies) — only the first category is ever auto-removable by this tool.
Only call propose_removal_pr when the user explicitly wants the safe subset actually removed, not just reported:
- It only touches unused imports on single-name import lines (
import x— neverfrom x import y, z, since removing the whole line would silently removeztoo). - It refuses on a dirty working tree — tell the user to commit or stash first if it reports that.
- It creates a branch, runs the repo's own real full test suite, and only commits/pushes/opens a PR if that suite actually passes. If
ghisn't installed/authenticated, the branch still gets pushed for real — only PR creation degrades. - A human still merges the PR — never describe this tool as having merged anything itself.
What not to do
Don't hand-remove dead code yourself with Edit/Write once this tool is available — route removals through propose_removal_pr so they stay gated on the real test suite, not your own judgment of what's safe. Don't report unused functions, classes, or dependencies as "safe to auto-remove" — only single-name unused imports are; everything else needs a human decision.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 26 lines · 144 tokens per session scan A c5f0c5c331ca
safe-fix-mcp is a skill published in the GitHub repository pamela-0/safe-fix-mcp (1 stars, last pushed 2mo ago), licensed MIT. It adds 144 tokens to every session and 570 once invoked, about $0.0006 per session on Opus 5.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
ai-development-guide
Applies language-agnostic and backend technical decision criteria, anti-pattern detection, debugging, and quality gates. Use when reviewing general/backend implementation choices, code smells, failures, or implementation completeness.
dorodango
Polishes working code through successive quality passes in fresh subagents. Use after tests pass when code needs multi-dimension refinement before release.
ring:searching-code
Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…
ring:using-assert
Using lib-observability/assert, Lerian's runtime assertion package, in two modes. Sweep Mode detects panic()/log.Fatal zero-panic violations, DIY invariant checks, hand-rolled domain predicates, and missing InitAssertionMetrics. Reference Mode catalogs the asserter lifecycle, domain predicates, observability trident…
ring:fixing-lint
Fixing lint to a clean state: runs the linter, groups reported issues into independent streams, and dispatches one parallel fixer agent per stream (ring:backend-go for Go, ring:general-purpose otherwise), iterating until clean. Use when a codebase has lint errors across multiple files. Skip for a single error (fix…
ring:detecting-goroutine-leaks
Detecting goroutine leaks in Go: greps for goroutine patterns, audits goleak coverage (VerifyTestMain/VerifyNone), runs goleak, and dispatches ring:backend-go to fix leaks and add regression tests. Use after implementation or during review when code spawns goroutines or a leak is suspected. Runs before…