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-depsgit 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-deps)<a href="https://agentmods.dev/skills/steph-dove/klaussy-agents/httpx-deps"><img src="https://agentmods.dev/badge/skills/steph-dove/klaussy-agents/httpx-deps/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/httpx-deps"><img src="https://agentmods.dev/badge/skills/steph-dove/klaussy-agents/httpx-deps.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.00061 | $0.01973 |
| Opus 5 | $0.00030 | $0.00986 |
| Sonnet 5 | $0.00012 | $0.00395 |
| Haiku 4.5 | $0.00006 | $0.00197 |
Grade A, and why
httpx-deps 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 11d 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
97% identical to fastapi-deps — 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upgrade dependencies without breaking the build. Move in small, verifiable steps — one batch at a time, tests green after each — rather than bumping everything at once and debugging the pile.
Phase 1: Survey
- Read CLAUDE.md for the package manager, the install command, and the test command.
- Read the manifest (
pyproject.toml,package.json,go.mod,Cargo.toml, …) and the lockfile. Note which versions are pinned exactly vs. ranged, and which deps are runtime vs. dev. - List what's outdated. Use the ecosystem's own tool (
pip list --outdated,npm outdated,go list -m -u all,cargo outdated). Separate the upgrades into:- patch/minor — low risk, batchable.
- major — has breaking changes; handle one at a time.
- Confirm a green baseline first. Run the test suite before changing anything. If it's already red, stop — you can't attribute a later failure to an upgrade.
Phase 2: Upgrade in order of risk
- Patch/minor first, as one batch. Bump them, reinstall, run the full suite. If green, keep going. If red, narrow to the culprit (bisect the batch) before proceeding.
- Then majors, one at a time. For each major bump:
- Read its changelog / migration notes for the version range you're crossing — grep the codebase for the APIs it says changed, and check whether you use them.
- Apply the bump and any required code changes together.
- Run the suite. Only move to the next major once green.
- Respect the pinning style. If the repo pins exact versions, pin the new exact version; if it uses ranges, keep the range form. Update the lockfile with the manager's own command — never hand-edit a lockfile.
Phase 3: Verify and summarize
- Run the full suite, lint, and build one final time on the fully-upgraded tree.
- Summarize what moved: package, old → new version, and for any major bump, the one-line reason it was safe (or the code change it required). Flag anything you couldn't fully verify.
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.
- 11d ago First seen · 73 lines · 61 tokens per session scan A 73e94b2f37ad
httpx-deps is a skill published in the GitHub repository steph-dove/klaussy-agents (16 stars, last pushed 14d ago), licensed MIT. It adds 61 tokens to every session and 1,973 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to fastapi-deps, 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.