iac-mcp: Agent for Claude Code

.claude/agents/issue-writer.md

issue-writer is an agent for Claude Code from jsavin/iac-mcp. It costs 17 tokens per session (2,149 once invoked), scanned A, original, MIT.

An issue-writing agent that turns development findings into GitHub issues following a project's labels and documentation rules.

In plain words
What is it for?
Use it to record bugs, technical debt, enhancements, and testing needs as properly organized GitHub issues.
Why use it?
It removes the effort of deciding how to structure, label, and explain detailed work items. It is intended for new issues, not simple questions or updates to existing ones.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions CLAUDE.md.

This is jsavin/iac-mcp's own configuration. It tells Claude Code how to work on iac-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything iac-mcp configures →

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /Users/jake/dev/jsavin/iac-mcp/src/jitd/parser.ts.

Reuse

Borrowing it

Nothing to install: this file belongs to jsavin/iac-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/jsavin/iac-mcp/main/.claude/agents/issue-writer.md
Clone the repo
git clone --depth 1 https://github.com/jsavin/iac-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for issue-writer

README.md
[![agentmods](https://agentmods.dev/badge/agents/jsavin/iac-mcp/issue-writer/github.svg)](https://agentmods.dev/agents/jsavin/iac-mcp/issue-writer)
Your own site
<a href="https://agentmods.dev/agents/jsavin/iac-mcp/issue-writer"><img src="https://agentmods.dev/badge/agents/jsavin/iac-mcp/issue-writer/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.

agentmods 80×15 button for issue-writer

Your own site · 80×15
<a href="https://agentmods.dev/agents/jsavin/iac-mcp/issue-writer"><img src="https://agentmods.dev/badge/agents/jsavin/iac-mcp/issue-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,149 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00017 $0.02149
Opus 5.5 $0.00007 $0.00860
Sonnet 5.5 $0.00003 $0.00430
Haiku 4.5 $0.00002 $0.00215

Measured 2mo ago against content hash 67a248ae8c9d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

.claude/agents/issue-writer.md · 194 lines

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.

Read the full file on GitHub · 194 lines

Changes

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.

  1. 2mo ago First seen · 194 lines · 0 tokens per session scan A 67a248ae8c9d

Subscribe to this mod's changes

issue-writer is an agent published in the GitHub repository jsavin/iac-mcp (3 stars, last pushed 7mo ago), licensed MIT. It adds 17 tokens to every session and 2,149 once invoked, about $0.0001 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-31.

Related

issue-writer compared with agents from other repositories

issue-writer next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
issue-writerjsavin/iac-mcpAgent37mo agoMITA17Claude Code
operatorPlocr/Reasonix-computer-useAgent433mo agoMITA20Claude Code
playwright-test-generatormicrosoft/playwrightAgent99kyesterdayApache-2.0A151Claude Code
.NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginnersAgent79k4d agoMITA33Claude Code
code-revieweranthropics/claude-cookbooksAgent54k2d agoMITA52Claude Code
AVM Owner Triagegithub/awesome-copilotAgent41kyesterdayMITA61Claude Code
Ultimate Transparent Thinking Beast Modegithub/awesome-copilotAgent41kyesterdayMITA11Claude Code