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-prgit 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-pr)<a href="https://agentmods.dev/skills/steph-dove/klaussy-agents/fastapi-pr"><img src="https://agentmods.dev/badge/skills/steph-dove/klaussy-agents/fastapi-pr/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-pr"><img src="https://agentmods.dev/badge/skills/steph-dove/klaussy-agents/fastapi-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00048 | $0.01748 |
| Opus 5 | $0.00024 | $0.00874 |
| Sonnet 5 | $0.00010 | $0.00350 |
| Haiku 4.5 | $0.00005 | $0.00175 |
Grade A, and why
fastapi-pr 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
1 near-identical copy found in the catalogue:
- httpx-pr — 98% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Branch
Run git branch --show-current and use its output.
Commit history vs base
Run git log master..HEAD --oneline and use its output.
Files changed
Run git diff master...HEAD --stat and use its output.
Instructions
Generate a PR description for the changes summarized above. Extract any ticket reference (e.g. FEAT-1234) from the branch name. Read CLAUDE.md for project conventions and any PR template rules. For key changed files, read them to understand the full context — do not paraphrase from the diff alone.
Output format:
## Summary
<!-- 1-3 sentences explaining what this PR does and why -->
## Changes
<!-- Bullet list of key changes, grouped logically -->
## Test Plan
<!-- How the changes were tested -->
- [ ] Tests pass locally
- [ ] Manually verified
## Notes
<!-- Anything reviewers should pay attention to, migration steps, feature flags, etc. -->
Rules:
- Write for a reviewer who has 30 seconds. Lead with what changed and why it matters; surface the one thing they must look at. The Summary should orient them before they open a single file.
- Don't echo the diff. The reviewer can read the diff. Summarize intent and group related changes — do not narrate every edit line by line.
- Describe the current end state, not a changelog. Write what the PR is, not a chronological story of how you got there ("first I tried X, then changed to Y"). If you revised an approach mid-branch, describe only the final shape.
- Be specific — reference actual file names, functions, and components.
- Focus on the "why" not just the "what".
- If the branch name has a ticket reference, include it in the summary.
- Keep it concise. No filler.
- If there are database changes, call them out explicitly.
- If there are new dependencies, mention them.
Write like a person, not a chatbot
Whatever you output for the user (comments, descriptions, messages) must read as if a human engineer wrote it. These rules mirror klaussy's deterministic humanizer (klaussy-desktop humanize-comment.js):
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 · 91 lines · 48 tokens per session scan A ffff03d3ddcf
fastapi-pr is a skill published in the GitHub repository steph-dove/klaussy-agents (16 stars, last pushed 13d ago), licensed MIT. It adds 48 tokens to every session and 1,748 once invoked, about $0.0002 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
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
gh-skill
Manage agent skills with gh skill. Use this skill to discover, preview, install, update, and publish Agent Skills so an agent can self-manage the skills available in its environment.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
conventional-commit
Conventional Commit - Generate Conventional Commits 1.0.0 compliant messages. MANDATORY for all git commits. Invoke when user says 'commit', 'commit this', or asks to commit code.
share-a-library
Use when a managed library is ready to publish to GitHub and hand to teammates as an install command. Run the GitHub publishing steps, then return the exact shareable install command.