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 helderberto/agent-skills --skill guidegit clone --depth 1 https://github.com/helderberto/agent-skillsWrote 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/helderberto/agent-skills/guide)<a href="https://agentmods.dev/skills/helderberto/agent-skills/guide"><img src="https://agentmods.dev/badge/skills/helderberto/agent-skills/guide/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/helderberto/agent-skills/guide"><img src="https://agentmods.dev/badge/skills/helderberto/agent-skills/guide.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.00022 | $0.01596 |
| Opus 5.5 | $0.00009 | $0.00638 |
| Sonnet 5.5 | $0.00004 | $0.00319 |
| Haiku 4.5 | $0.00002 | $0.00160 |
Grade A, and why
guide 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guide
You don't remember every skill, so ask. Map $ARGUMENTS (empty → ask what the user is trying to do) to the skill or flow that fits, and end on one filled-in Next: line. Before you state what a skill does or recommend skipping one, read its SKILL.md: this map is orientation only.
The map
A flow is a path through the skills. Most work runs along the main flow; on-ramps merge onto it. Everything else is standalone, or a vocabulary layer underneath.
Main flow: idea → PR
/hb:triageclassifies the input, sizes it, and names the entry. S work skips to/hb:build; M work with a crisp ticket skips to/hb:to-tickets./hb:grillsharpens the idea by interview, in rounds over the design-tree frontier. It writes settled terms toGLOSSARY.md(viadomain-modeling) and hard-to-reverse decisions to ADRs (viato-adr) as they land.- A question needs a runnable answer? A state model, business logic, a UI you have to see → detour through
/hb:prototype, kept on aprototype/<name>branch, then back to the grill with what you learned.
- A question needs a runnable answer? A state model, business logic, a UI you have to see → detour through
/hb:to-specturns the settled conversation into.specs/specs/<slug>.md. No interview: an open branch sends you back to/hb:grill./hb:to-ticketsslices the spec into tracer-bullet tickets in.specs/tickets/<slug>.md, each with blocking edges. Only exceptions get ahitllabel./hb:buildimplements the next unblocked ticket test-first throughtdd, runscheck, and commits.--allfans the tickets out to parallel implementer subagents, frontier by frontier, after one approval, and stops before eachhitlone./hb:reviewfans out parallel reviewers: correctness, standards, spec conformance with ticket checkboxes, test effectiveness with changed-line coverage, the quality bar, and the audits the diff calls for./hb:to-pris the only command that publishes: gate, an optional--safesecret scan, push, PR body with evidence and merge danger,gh pr create, CI watch./hb:retrocloses the loop. It suggests changes to the agent's environment, not the code: navigation pointers, checks, coding standards, steering files. Mechanical mistakes become checks; judgement calls become standards.
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.
- 3d ago Changed · +1 lines b72427e32622
- 4d ago First seen · 80 lines · 22 tokens per session scan A eb8176b96f78
guide is a skill published in the GitHub repository helderberto/agent-skills (17 stars, last pushed 3d ago), licensed MIT. It adds 22 tokens to every session and 1,596 once invoked, about $0.0001 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-10-12.
Other skills, from other repositories
jupyter
Expert Jupyter Notebook assistance covering interactive Python, kernels, ipywidgets, magic commands, and reproducible data science. Use when prototyping data analysis, ML experiments, and interactive visualizations.
code-explanation
Get layered, context-aware explanations of unfamiliar code. Understand what it does, why it was written that way, and how to work with it safely.
context-engineering
Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.
doubt-driven-development
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stakes are high…
performance-optimization
Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.
test-driven-development
Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality. Use when asked to add tests to a function, fix a bug…