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.
git clone --depth 1 https://github.com/jabrena/plinthWrote 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/jabrena/plinth/update-issue)<a href="https://agentmods.dev/commands/jabrena/plinth/update-issue"><img src="https://agentmods.dev/badge/commands/jabrena/plinth/update-issue/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/commands/jabrena/plinth/update-issue"><img src="https://agentmods.dev/badge/commands/jabrena/plinth/update-issue.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.00011 | $0.00387 |
| Opus 5.5 | $0.00004 | $0.00155 |
| Sonnet 5.5 | $0.00002 | $0.00077 |
| Haiku 4.5 | $0.00001 | $0.00039 |
Grade A, and why
update-issue 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 1mo 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.
What it actually says
update-issue
Update an existing project issue description with structured, evidence-backed content.
Usage
/update-issue <issue> [<source>] [<tracker>]
Accepted Inputs
- Existing GitHub or Jira issue number, key, or URL
- Optional source notes, supporting discussion, user story, acceptance criteria, or file path
- Optional tracker selection: GitHub or Jira
Owning Agent
@plinth-business-analyst
Associated Skills
043-planning-github-issues044-planning-jira045-planning-azure-devops014-agile-user-storywhen user-story refinement is required
Workflow
- Load the current issue description and relevant discussion before drafting changes.
- Confirm the requested update scope and the source material authority.
- Use
014-agile-user-storywhen the update needs user-story, acceptance-criteria, or Gherkin-style structure. - Draft the updated issue body without inventing requirements.
- Present the proposed body before overwriting the existing issue description.
- Update the issue in the selected tracker after approval.
- Report the issue identifier and URL.
Output
- Updated structured issue description
- Acceptance criteria or user-story scenario when applicable
- Updated GitHub/Jira issue reference
Safeguards
- Do not invent requirements, acceptance criteria, or comments.
- Do not expose tracker credentials or tokens.
- Do not overwrite an issue body without showing the proposed replacement.
- Preserve relevant existing issue content unless the user explicitly asks to remove it.
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.
- 1mo ago First seen · 60 lines · 11 tokens per session scan A 71c5663eb7b3
update-issue is a command published in the GitHub repository jabrena/plinth (452 stars, last pushed 2d ago), licensed Apache-2.0. It adds 11 tokens to every session and 387 once invoked, about $0.0000 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-08-30.
Other commands, from other repositories
epic-plan
Run /epic-plan — see .claude/commands/epic-plan.md for the authoritative spec.
prd
Use when writing a PRD or business case — is this worth building, for whom, at what priority (Google/Amazon/Stripe methodologies).
idea
Use when exploring a new idea — validates demand, analyzes competitors, and checks for pseudo-requirements before writing specs.
start
Run the shorts pipeline across long-lived tmux panes. /start for a fresh run, or /start to reuse an already-ingested video. Each phase shows its progress in the foreground; tmux attach -t to inspect any phase live.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.