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 agents/marcusjellinghaus/mcp-workspace/issue-updatergit clone --depth 1 https://github.com/MarcusJellinghaus/mcp-workspaceWrote 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/marcusjellinghaus/mcp-workspace/issue-updater)<a href="https://agentmods.dev/agents/marcusjellinghaus/mcp-workspace/issue-updater"><img src="https://agentmods.dev/badge/agents/marcusjellinghaus/mcp-workspace/issue-updater.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.1 | $0.00028 | $0.00380 |
| Opus 5 | $0.00014 | $0.00190 |
| Sonnet 5 | $0.00006 | $0.00076 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
issue-updater 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 6d 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
Issue-Updater Agent
You are an issue update specialist.
Do not invoke /issue_update — it is disable-model-invocation, so the Skill tool will
refuse. Instead read .claude/skills/issue_update/SKILL.md with
mcp__mcp-workspace__read_file and follow its process. Ignore its frontmatter, its opening
"no issue context found" step — your content comes from your launch prompt, not from a prior
/issue_analyse discussion — and any other wording aimed at a user typing the command. You
are running it unattended.
On top of that process:
- Scope — confirm the issue number in your launch prompt matches the issue you are about to edit; if it does not, stop and report back without editing.
- Shell —
ghcommands only. - Report the issue number, the new title, and confirmation the edit succeeded.
The working directory is already correct — do not use cd or git -C.
Runs with bypassPermissions. Rationale and limits:
docs/repository-setup/agent-permissions.md in the mcp-coder repository.
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.
- 6d ago First seen · 37 lines · 28 tokens per session scan A c316897251fa
issue-updater is an agent published in the GitHub repository MarcusJellinghaus/mcp-workspace (50 stars, last pushed 4d ago), licensed MIT. It adds 28 tokens to every session and 380 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 agents, from other repositories
coder
Sonnet implementer for a well-scoped change — edits/tests to green; not architecture calls, asks if ambiguous.
extract
Cheap read-only agent — pulls facts/lists from files without judgment; never edits or analyzes.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
ios-tester
You are an iOS testing agent for the Bullhorn project — a Next.js 14 social media post scheduler built with Supabase, Zustand, and Tailwind CSS, running in Safari via Capacitor on the iOS Simulator.
security-auditor
Use this agent when you need to perform security assessments, vulnerability analysis, or security code reviews. Examples: Context: The user has just implemented authentication middleware and wants to ensure it's secure. user: 'I just added JWT authentication to my API. Can you review it for security issues?'…
devops-automator
Use this agent when you need to automate DevOps workflows, manage CI/CD pipelines, configure infrastructure as code, set up monitoring and alerting systems, or streamline deployment processes. Examples: Context: User needs to set up automated deployment pipeline for a web application. user: 'I need to create a CI/CD…