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/and3r817/dot-claude-plugins/gh-cli-statusgit clone --depth 1 https://github.com/and3r817/dot-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/and3r817/dot-claude-plugins/gh-cli-status)<a href="https://agentmods.dev/commands/and3r817/dot-claude-plugins/gh-cli-status"><img src="https://agentmods.dev/badge/commands/and3r817/dot-claude-plugins/gh-cli-status.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.00006 | $0.00151 |
| Opus 5 | $0.00003 | $0.00076 |
| Sonnet 5 | $0.00001 | $0.00030 |
| Haiku 4.5 | $0.00001 | $0.00015 |
Grade B, and why
gh-cli-status 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 4d 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.
1. Read `~/.claude/settings.json` and check `githubWriteGuard.enabled` status (defaults to enabled if not set) What it actually says
Check the GitHub CLI security guard status.
Tasks:
- Read
~/.claude/settings.jsonand checkgithubWriteGuard.enabledstatus (defaults to enabled if not set) - Display the status
Output format:
🛡️ GitHub CLI Security Guard
Status: [ENABLED/DISABLED]
The security guard blocks all GitHub CLI write operations:
- Repository modifications (create, delete, archive)
- PR/Issue changes (create, merge, close)
- API write methods (POST, PUT, PATCH, DELETE)
- Workflow operations (run, cancel)
Read operations are always allowed.
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.
- 4d ago First seen · 28 lines · 6 tokens per session scan B 438238fb65fd
gh-cli-status is a command published in the GitHub repository and3r817/dot-claude-plugins (2 stars, last pushed 8mo ago), licensed MIT. It adds 6 tokens to every session and 151 once invoked, about $0.0000 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
configure
Configure which Fizzy.do board to sync todos to.
sync
Manually trigger todo sync to Fizzy.do.
status
Show Fizzy.do connection and sync status.
setup
Connect your Fizzy.do account.
plan-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results.
better-auth:setup
Interactive setup wizard for better-auth authentication. Guides through database, framework, OAuth providers, and plugin configuration.