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 steph-dove/klaussy-agents --skill fastapi-fixgit clone --depth 1 https://github.com/steph-dove/klaussy-agentsWrote 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/steph-dove/klaussy-agents/fastapi-fix)<a href="https://agentmods.dev/skills/steph-dove/klaussy-agents/fastapi-fix"><img src="https://agentmods.dev/badge/skills/steph-dove/klaussy-agents/fastapi-fix/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/steph-dove/klaussy-agents/fastapi-fix"><img src="https://agentmods.dev/badge/skills/steph-dove/klaussy-agents/fastapi-fix.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.00055 | $0.00909 |
| Opus 5 | $0.00028 | $0.00454 |
| Sonnet 5 | $0.00011 | $0.00182 |
| Haiku 4.5 | $0.00006 | $0.00091 |
Grade A, and why
fastapi-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 10d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- httpx-fix — 98% identical, 2 lines differ
- {{REPO}}-fix — 92% identical, 7 lines differ
How it starts
The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix all lint, format, and type errors in the current changes.
Steps
-
Read CLAUDE.md to find the project's lint, format, and type-check commands. If they're missing, fall back to the stack defaults below.
-
Read any
.claude/rules/*.mdwhosepaths:glob matches the files you're about to touch — they may carry style/typing rules the linter doesn't enforce. -
Scope to this branch's change. Build the changed-file list — the union of:
git diff --name-only master...HEAD(work committed on this branch)git diff --name-only(unstaged) andgit diff --name-only --cached(staged)
Pass these paths to every command below so the tools judge only what this branch changed — never the whole repo. Pre-existing violations in untouched files are not yours to fix here. If the list is empty, there's nothing to fix; say so and stop. (If
master...HEADerrors because the base branch isn't present locally, fall back to the uncommitted diff alone.) -
Run each command in this order, scoped to the changed files (apply each pass before running the next, so fixes from one don't fight the next):
- Format first (it normalizes whitespace and quoting that lint rules might complain about).
- Lint next (it picks up real style/safety issues on top of formatted code).
- Type-check last (type errors don't move under format/lint, but the line numbers will). If the type-checker needs whole-project context to resolve imports, run it normally but only fix errors that land in the changed files.
-
Fix all reported issues. When format and lint disagree on a specific construct, lint wins (formatters auto-resolve; lint encodes intent).
-
Re-run all three (still scoped to the changed files) to verify they're clean.
Stack defaults (if CLAUDE.md doesn't specify commands)
Append the changed files to each command (e.g. ruff check <files>) so it stays scoped to the branch's change.
- Python:
ruff format,ruff check,mypy(orpyright) - TypeScript / JavaScript:
prettier --write,eslint --fix,tsc --noEmit(tscchecks the whole project — read only the changed files' errors) - Go:
gofmt -w/goimports -w,go vet,staticcheck - Rust:
cargo fmt,cargo clippy --fix,cargo check(cargo works per-crate — limit fixes to the changed files)
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.
- 10d ago First seen · 47 lines · 55 tokens per session scan A e6de85cf60e4
fastapi-fix is a skill published in the GitHub repository steph-dove/klaussy-agents (16 stars, last pushed 13d ago), licensed MIT. It adds 55 tokens to every session and 909 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
rust-check
Run cargo check on the current Rust project to find compile errors.
printing-press-polish
Polish a generated CLI to pass verification and become publish-ready. Runs diagnostics (dogfood, verify, scorecard, go vet, gosec), automatically fixes all issues (verify failures, static-analysis findings, dead code, descriptions, README, MCP tool quality), reports the before/after delta, and offers to publish. Use…
agent-inspect
Local evidence debugger and trajectory-test toolkit for TypeScript AI agents. Use when capturing framework-faithful traces, asserting TraceContract/TraceFacts, packaging Evidence v2, or inspecting local runs over read-only MCP (gettracefacts).
pi-loop-forensics
Diagnose pi-go agent loops and degenerate turns — "agent loop aborted", runaway thinking with no tool calls, repeated phrases. Discriminates genuine model repetition collapse from a race, a tool-parse failure, or a too-low guard, and A/B replays a seed session across providers.
nightly-session-watch
Nightly sweep of the last 24h of pi-go sessions — anomalous runs, loop aborts, tool error rates, token waste, real prompt-token spend, and whether the observation and palace pipelines are still recording. Triages each finding to the specialist skill that diagnoses it. Use for an unattended daily health check, or on…
angular
Use when building, refactoring, or debugging Angular (v20/21+): standalone components, signals, zoneless change detection, @if/@for/@defer control flow, inject() DI, resource()/httpResource(), RxJS interop, NgRx SignalStore, ng CLI. NOT React (that is react), NOT Next.js (that is nextjs), NOT a TypeScript language…