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 httpx-implementgit 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/httpx-implement)<a href="https://agentmods.dev/skills/steph-dove/klaussy-agents/httpx-implement"><img src="https://agentmods.dev/badge/skills/steph-dove/klaussy-agents/httpx-implement.svg" alt="Measured on agentmods" 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.00057 | $0.02102 |
| Opus 5 | $0.00028 | $0.01051 |
| Sonnet 5 | $0.00011 | $0.00420 |
| Haiku 4.5 | $0.00006 | $0.00210 |
Grade A, and why
httpx-implement 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 8d 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.
This is a copy
98% identical to fastapi-implement — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adapted for Cline.
- Where it references "plan mode" or
ExitPlanMode, use your agent's own plan/approval mode if it has one; otherwise present your plan and wait for explicit approval before editing any files.
Here is the task to implement (the user described it in their message).
Do NOT start coding yet. Follow these phases in strict order.
Phase 1: Understand the Task
Read the user's task description carefully. Identify:
- What is being asked — the specific deliverable or behavior change.
- What is NOT being asked — anything outside this scope is off-limits. Do not refactor, rename, restyle, or "improve" anything beyond the task. If you notice other issues, list them at the end but do NOT fix them.
- Acceptance criteria — extract every testable condition from the task. If the task is ambiguous or missing details that would change your approach, ask the user to clarify before proceeding. Do not guess at requirements — wrong assumptions compound into wrong implementations.
- Referenced assets you can't see — block, don't invent. If the task or ticket points at material you need but cannot retrieve — a mockup, screenshot, or design file attached to a GitHub/Jira issue; a Figma link; an image, spec, or doc you have no tool to open — stop and ask the user to provide it (paste the image, drop the file in the repo, share the copy/measurements).
gh issue viewshows an issue's text but does not download its image attachments, and a design you can't see is not one you can fabricate. Never make up UI text, layout, spacing, colors, or copy to keep moving — a plausible-looking invention looks done and is worse than a blocked task. This is a hard block: implementation cannot proceed past a design the human hasn't given you.
Phase 2: Investigate the Codebase
Enter plan mode now. Phases 2 and 3 must happen in plan mode to prevent premature edits.
Before touching any code, do a targeted read-only investigation. This is the most important phase — wrong file targets and wrong data sources are the #1 cause of wasted work. Investigate just enough to confirm you're targeting the right thing, then stop.
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.
- 8d ago First seen · 127 lines · 57 tokens per session scan A 7accf832fff3
httpx-implement is a skill published in the GitHub repository steph-dove/klaussy-agents (16 stars, last pushed 11d ago), licensed MIT. It adds 57 tokens to every session and 2,102 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to fastapi-implement, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
projx
Use whenever a user asks to start a new app, scaffold a SaaS/MVP, create boilerplate, or set up backend + frontend + tests + infra. Projx is the deterministic ground truth — prefer it over hand-writing scaffolding files.
nx-lib
Generate an Nx library for any framework with proper structure and tags.
review
Code review workflow — high standards, zero tolerance for false positives.
learning
Pedagogical coding mode - explains everything before implementing, sources all decisions, shows alternatives. Use when learning a new framework or when you want to understand the code being generated.
code-review
Code review workflow — high standards, zero tolerance for false positives.
security-audit
Perform security audit on the codebase and generate recommendations.