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 setupgit 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/setup)<a href="https://agentmods.dev/skills/helderberto/agent-skills/setup"><img src="https://agentmods.dev/badge/skills/helderberto/agent-skills/setup/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/setup"><img src="https://agentmods.dev/badge/skills/helderberto/agent-skills/setup.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.00025 | $0.00473 |
| Opus 5.5 | $0.00010 | $0.00189 |
| Sonnet 5.5 | $0.00005 | $0.00095 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
setup 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 today.
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.
What it actually says
Setup
Per repo. Records where every flow skill keeps specs and tickets. No config → markdown under .specs/, the default. GitHub or Jira → only in that tracker. Rerun to switch: new work follows the new choice, nothing migrates.
1. Explore
git remote -v: GitHub remote?.specs/issue-tracker.md: prior output of this skill?git check-ignore -q .specs: already ignored?
2. Ask one question
Argument given (local, github, jira <KEY>) → skip the question. Otherwise: which tracker? Lead with the recommendation: GitHub when the remote is on GitHub, else local.
- GitHub →
ghCLI - Jira → ask the project key; Atlassian MCP
- Local → markdown in
.specs/only
3. Write
Never touch committed files: no AGENTS.md, CLAUDE.md, or .gitignore edits. The skills read the config directly.
Local → remove .specs/issue-tracker.md if present; skills fall back to issue-tracker-local.md. Done.
GitHub / Jira → copy the seed (issue-tracker-github.md or issue-tracker-jira.md) to .specs/issue-tracker.md, filling the placeholders.
.specs/ not ignored → append .specs/ to .git/info/exclude: ignored for this clone, never committed.
GitHub + hitl label missing → gh label create hitl --force.
4. Done
Print the tracker chosen and the files written. Switching later: rerun, or edit .specs/issue-tracker.md.
Next: /hb:triage or /hb:grill <idea>.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 43 lines · 0 tokens per session scan A 658233764e40
setup is a skill published in the GitHub repository helderberto/agent-skills (17 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 473 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-17.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
monorepo-architect
Expert guide for designing and managing scalable monorepos using Turborepo, pnpm workspaces, and shared packages / Panduan ahli untuk merancang dan mengelola monorepo skalabel menggunakan Turborepo dan pnpm workspaces.
cast-conflicts
Before editing or fanning out work, find the live sessions on this repository that are changing the same files, show what they changed, and warn them. Use before starting a task that touches shared files, before spawning workers, or when asked who else is working on this.
git-workflow-and-versioning
A guide to using Git, a system for tracking code changes, branches, and saved versions. It recommends small, focused commits and short-lived feature branches while keeping the main branch deployable.
shipping-and-launch
A production-release checklist and planning guide for putting software in front of real users. It covers testing, security, monitoring, staged rollout, and rollback, which means returning to the previous working version.
argocd
Expert Argo CD GitOps assistance covering Application CRDs, sync policies, automated self-healing, Helm/Kustomize, and multi-cluster deployments. Use when managing Kubernetes deployments via GitOps.