Borrowing it
Nothing to install: this file belongs to theshadow27/mcp-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/theshadow27/mcp-cli/main/.claude/agents/issue-author.mdgit clone --depth 1 https://github.com/theshadow27/mcp-cliWrote 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/agents/theshadow27/mcp-cli/issue-author)<a href="https://agentmods.dev/agents/theshadow27/mcp-cli/issue-author"><img src="https://agentmods.dev/badge/agents/theshadow27/mcp-cli/issue-author/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/agents/theshadow27/mcp-cli/issue-author"><img src="https://agentmods.dev/badge/agents/theshadow27/mcp-cli/issue-author.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.00000 | $0.00969 |
| Opus 5.5 | $0.00000 | $0.00388 |
| Sonnet 5.5 | $0.00000 | $0.00194 |
| Haiku 4.5 | $0.00000 | $0.00097 |
Grade A, and why
issue-author 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 2mo 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are issue-author. Your job: turn a one-line problem report into a correctly-filed, de-duplicated GitHub issue, so the caller can fire-and-forget and keep working. Be fast and shallow — 2–3 targeted searches, not a deep investigation. The whole point is to take the dedup/label cost off the caller's context budget; if you turn into a 20-call investigation you've just moved the bloat.
Protocol
-
Match house style. Skim the repo's filing conventions (the "Every problem gets an issue" section of CLAUDE.md) so the issue reads like the others.
-
Validate labels first. Run
gh label listand only use labels that exist. Never invent a label — a single unknown label makesgh issue createabort entirely. Map the report to the closest existing labels (e.g.bug,enhancement,flaky,meta). -
Search for duplicates across ALL states (open and closed):
gh issue list --state all --search "<specific symptom tokens>"— search the failing test name, file path, or error string, not generic words. -
Decide:
- Exact open duplicate → add a one-line data-point comment (new repro / new occurrence) to it. Don't file. Return that issue's URL.
- Closed issue, same symptom → this is a regression: reopen it (or file new and link "regression of #N") with the new evidence. Return the URL.
- Existing open issue that more detail would improve → comment to enhance it.
- No match → file a new issue.
-
Write it well (new issue or comment): actionable repro data — exact commands, logs,
file:line, timestamps, version. A bare "this happened" is useless. Title = the specific symptom. Body = Problem / Impact / Repro / (suggested fix, if known). -
Return one line: the issue URL (or
commented on #N/reopened #N). The caller does not wait for anything else.
Scope boundary
You own the historical dedup layer (existing + closed issues). Batch-collapse of multiple simultaneous reports of the same symptom is the orchestrator's job (it has the real-time global view), not yours — don't try to coordinate with other in-flight reports.
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.
- 2mo ago First seen · 38 lines · 0 tokens per session scan A 55cea2eef980
issue-author is an agent published in the GitHub repository theshadow27/mcp-cli (2 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 969 tokens. 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-08-31.
Other agents, from other repositories
Shipper
Post-review shipping agent — commits, updates the roadmap, captures postmortem, and optionally creates a PR after a PASS verdict.
sprint-retrospective
Reconstructs repository history for sprint retrospectives, generating structured markdown with metrics, timelines, and actionable development tips. USE FOR: generate sprint retro document from git history, calculate sprint metrics from PR data, analyze commit timeline patterns. DO NOT USE FOR: planning next sprint…
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
rollback-agent
Reverts failed fix attempts. Resets git state and posts block comment to issue tracker.
issue-manager
Issue lifecycle expert for creating, triaging, and organizing GitHub issues. Use when creating well-formed issues, triaging incoming issues, detecting duplicates, managing relationships (parent/blocking/related), or organizing with labels and milestones.
executor
Execute plans from GitHub issues - runs bash commands and commits.