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 agentmods add commands/muloka/claude-plugins/agent-helpers-setupgit clone --depth 1 https://github.com/muloka/claude-pluginsWrote 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/commands/muloka/claude-plugins/agent-helpers-setup)<a href="https://agentmods.dev/commands/muloka/claude-plugins/agent-helpers-setup"><img src="https://agentmods.dev/badge/commands/muloka/claude-plugins/agent-helpers-setup.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 | $0.00022 | $0.00676 |
| Opus 5 | $0.00011 | $0.00338 |
| Sonnet 5 | $0.00004 | $0.00135 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade B, and why
agent-helpers-setup scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- add four `Bash(jj…:*)` entries to `permissions.allow` in `~/.claude/settings.json` The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 First seen · 48 lines · 22 tokens per session scan B 190885aca09d
agent-helpers-setup is a command published in the GitHub repository muloka/claude-plugins (6 stars, last pushed 2d ago), with no licence file. It adds 22 tokens to every session and 676 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
derive-tests
Turn documented intent into a test-coverage map — inventory the tests that exist today, derive use-case cases from the system docs, separate existing coverage from proposed tests and unverified gaps, mark each unit / guarded-live / manual, and recommend a green-before-merge CI gate.
ship-check
Turn a vibe-coded repo into a reviewer-ready shipping packet — document the app, wire agent context, run security and performance audits, map test coverage, and compile the results.
competitive-analysis
Analyze the competitive landscape — identify competitors, compare strengths and weaknesses, find differentiation opportunities.
providers
Display Better Auth available authentication providers and their configuration.
commit
Create well-formatted commits with conventional commit messages and emojis.
sheet-report
Analyze a Numbers or Excel file and generate a report with charts.