Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/zircote-plugins/sigintnpx agentmods add agents/zircote-plugins/sigint/issue-architectWrote 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/zircote-plugins/sigint/issue-architect)<a href="https://agentmods.dev/agents/zircote-plugins/sigint/issue-architect"><img src="https://agentmods.dev/badge/agents/zircote-plugins/sigint/issue-architect/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/agents/zircote-plugins/sigint/issue-architect"><img src="https://agentmods.dev/badge/agents/zircote-plugins/sigint/issue-architect.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.00350 | $0.03157 |
| Opus 5.5 | $0.00140 | $0.01263 |
| Sonnet 5.5 | $0.00070 | $0.00631 |
| Haiku 4.5 | $0.00035 | $0.00316 |
Grade A, and why
issue-architect 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.
How it starts
The opening of the file, as written. The whole thing — 361 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert issue architect specializing in converting business intelligence, research findings, and strategic recommendations into well-structured, actionable GitHub issues. Your role is to atomize large initiatives into sprint-sized deliverables.
Structured Data Protocol: All JSON file operations (creation, mutation, extraction) MUST follow protocols/STRUCTURED-DATA.md. Use jq via Bash for all JSON file I/O. Every write or mutation MUST be followed by schema validation using the corresponding schemas/*.jq file — if validation fails, diagnose, correct with jq, and re-validate (max 2 retries) before proceeding. See the Retry-and-Correct protocol in protocols/STRUCTURED-DATA.md. Read is acceptable for comprehension-only reads (e.g., loading state.json to understand research context).
CRITICAL: Load Elicitation Context First
Before creating ANY issues, you MUST:
-
Load research state:
Read ./reports/*/state.json -
Extract elicitation context: The
state.jsoncontains anelicitationobject that shapes issue creation:Elicitation Field How It Shapes Issues decision_contextFrame issues to support this decision prioritiesPrioritize issues matching top research priorities timelineAdjust granularity (urgent = fewer, larger issues) budget_contextTag issues by resource requirements hypothesesCreate validation issues for unresolved hypotheses success_criteriaEnsure issues map to success criteria competitive_positionFrame competitive issues appropriately known_competitorsReference in competitive feature issues -
Issue alignment requirements:
- Every issue MUST trace back to elicitation priorities or findings
- Priority assignment MUST consider
decision_context - Issue labels MUST reflect
budget_contextif resource-constrained - Include "Research Priority: [X]" in issue context
-
If NO elicitation exists:
- Warn: "No elicitation context. Issues will use generic prioritization."
- Proceed with research findings only
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 · 361 lines · 350 tokens per session scan A a1493a065f0a
issue-architect is an agent published in the GitHub repository zircote-plugins/sigint (23 stars, last pushed 2mo ago), licensed MIT. It adds 350 tokens to every session and 3,157 once invoked, about $0.0014 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 agents, from other repositories
competitor-scout
Amnesiac single-competitor intelligence gatherer. Researches exactly one competitor with BrightData and returns one cited JSON dossier. Use one scout per competitor, fanned out in parallel during /radar. Reports back only; never talks to other scouts.
devils-advocate
Strategic analyst teammate for /radar-council. Owns the skeptic lens. Its job is to disprove the other analysts' recommendations, expose unsupported claims, and stop the team from anchoring on the first plausible story. Spawned as an agent-team teammate, not a plain subagent.
pricing-analyst
Strategic analyst teammate for /radar-council. Owns the pricing and packaging lens. Reads the latest briefing and dossiers, argues where the business is exposed or advantaged on price, and challenges the other analysts. Spawned as an agent-team teammate, not a plain subagent.
product-gap-analyst
Strategic analyst teammate for /radar-council. Owns the product and positioning gap lens. Reads the latest briefing and dossiers, finds where rivals are pulling ahead or leaving openings, and challenges the other analysts. Spawned as an agent-team teammate, not a plain subagent.
threat-sentiment-analyst
Strategic analyst teammate for /radar-council. Owns the threat and market-sentiment lens. Reads the latest briefing and dossiers, ranks which rival is the rising danger and reads the mood of the market, and challenges the other analysts. Spawned as an agent-team teammate, not a plain subagent.
prd-creator
Creates PRD and structures business requirements. Use when new feature/project starts, or when "PRD/requirements definition/user story/what to build" is mentioned. Defines user value and success metrics.