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/jabrena/plinth/update-issuegit clone --depth 1 https://github.com/jabrena/plinthWhat 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.00011 | $0.00387 |
| Opus 5 | $0.00005 | $0.00193 |
| Sonnet 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 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.
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.
- 3d ago First seen · 60 lines · 11 tokens per session scan A 71c5663eb7b3
update-issue is a command published in the GitHub repository jabrena/plinth (435 stars, last pushed 2d ago), licensed Apache-2.0. It adds 11 tokens to every session and 387 once invoked, about $0.0001 per session on Opus 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
gm-brilliant-implementation
Run the complete 34-stage implementation workflow for a large, multi-system, multi-wave, or CPU-delegated 5 Star Booker GM program.
chain
Run an ad-hoc ordered chain of pm-skills with shared context (ephemeral; routes to the pm-workflow-orchestrator).
update-pm-skills
Update local pm-skills installation to the latest public release with conflict-aware overwrite-or-skip options and a detailed change report.
get-to-work
Autonomous ops work. Args: [mode] [repeat]. Modes: tasks | opps | full | escalating (default). Repeat: cycle (keep going, default) | once (single pass). Run this before stepping away from an ops repo.
recap
Summarize what happened in the project since a given date. Produces a short lead on what's different now, backed by tables and lists covering completed work, state changes, backlog movement, and key decisions. Use when the user wants to catch up on project activity, review recent progress, or generate a status update…
whats-next
Generate an executive overview of the project. Synthesizes state, backlogs, and recent plans into a ranked action plan answering "What should we do next?".