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/zircote-plugins/sigint/issuesgit clone --depth 1 https://github.com/zircote-plugins/sigintWhat 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.00129 |
| Opus 5 | $0.00005 | $0.00064 |
| Sonnet 5 | $0.00002 | $0.00026 |
| Haiku 4.5 | $0.00001 | $0.00013 |
Grade A, and why
issues 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 yesterday.
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
Load and execute the sigint:issues skill with these arguments: $ARGUMENTS
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.
- yesterday First seen · 9 lines · 0 tokens per session scan A a9933c48a7a8
issues is a command published in the GitHub repository zircote-plugins/sigint (20 stars, last pushed 15d ago), licensed MIT. It adds 11 tokens to every session and 129 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
radar-council
The on-demand strategic war room. Spins up a REAL experimental agent team of 4 analyst teammates (pricing, product gap, threat and sentiment, devil's advocate) over the latest briefing. They message and challenge each other like a scientific debate, converge on recommended moves, and the addendum is published to all…
radar
The weekly competitor gather run. Fans out one competitor-scout subagent per competitor in parallel, each returning a cited dossier via BrightData, then diffs against last week, merges one briefing, and publishes to all three surfaces (local folder, Notion, HTML dashboard). Runs autonomously. Run /radar-setup first.
radar-setup
One-time setup for Competitive Intelligence Radar. Asks about your BrightData and Notion connection and live-tests both, then shows the proposed Notion schema for your approval before creating anything, then checks the agent-teams prerequisites for the council. Run this before /radar.
build-market-research
Build comprehensive market research with industry analysis, future trends, and strategic opportunities.
agent-improve
Review this conversation and generate a structured improvement report.
uxbot-aggregate
Aggregate per-task UXBot reports into an overall UX report, looking for patterns across tasks.