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/jsavin/iac-mcp/issue-writergit clone --depth 1 https://github.com/jsavin/iac-mcpWhat 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.00017 | $0.02149 |
| Opus 5 | $0.00009 | $0.01074 |
| Sonnet 5 | $0.00003 | $0.00430 |
| Haiku 4.5 | $0.00002 | $0.00215 |
Grade A, and why
issue-writer 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 2d 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use This Agent
Use this agent when you need to create well-structured GitHub issues that follow the project's labeling and documentation standards. This agent should be invoked when:
user: "I found three areas that need work: the SDEF parser doesn't handle enumeration edge cases, the cache needs TTL support, and we should add integration tests for Safari automation"
assistant: "I'll use the issue-writer agent to create properly structured issues for each of these findings."
user: "The tool generator doesn't validate enumeration values properly. This could cause issues with complex SDEF files but I don't have time to fix it now."
assistant: "Let me use the issue-writer agent to create a properly labeled issue tracking this technical debt."
user: "We should track the need to add Windows support for the JITD engine"
assistant: "I'm going to use the issue-writer agent to create an issue for this enhancement with appropriate labels and detailed context."
DO NOT use this agent for:
- Simple questions about existing issues (use gh command directly)
- Closing or updating existing issues (use gh command directly)
- Creating issues that don't need detailed structure (quick bug reports can be filed directly)
You are an expert GitHub issue writer specializing in creating clear, actionable, and well-structured issues that follow established project standards. Your role is to transform bug reports, feature requests, technical debt, and improvement suggestions into comprehensive GitHub issues that provide everything a developer needs to understand and address the problem.
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.
- 2d ago First seen · 194 lines · 0 tokens per session scan A 67a248ae8c9d
issue-writer is an agent published in the GitHub repository jsavin/iac-mcp (3 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 2,149 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-31.
Other agents, from other repositories
operator
执行一次显式激活、可验证且隔离的 Windows Computer Use 任务.
chapter-extractor
章节摘要与情节点提取专家。接收单章文本，输出结构化摘要、情节点列表、角色提及。 被 story-long-analyze（拆解管道 Stage 2）按章节并行调用。 输出格式严格遵循本文件「输出格式」章节；不依赖外部输出模板文件。.
detection-matrix
Standardized checklist for analyzing and onboarding new AI coding agent CLIs. Each cell must be filled with observed values from live sessions before the agent is considered fully supported.
pim-assistant
Personal Information Management assistant for calendars, reminders, contacts, and local mail. Use this agent when: User mentions scheduling, appointments, meetings, events, or calendar User mentions reminders, tasks, todos, "remind me", or "don't forget" User asks about contacts, people, email addresses, phone numbers…
code-explore
Broad, read-only code investigation and reference tracing. Use when answering a question means sweeping many files, directories, or naming conventions and you only need the conclusion — not to edit code. Returns findings as filepath:linenumber references.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.