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.
git clone --depth 1 https://github.com/zircote-plugins/sigintWrote 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/commands/zircote-plugins/sigint/status)<a href="https://agentmods.dev/commands/zircote-plugins/sigint/status"><img src="https://agentmods.dev/badge/commands/zircote-plugins/sigint/status/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/commands/zircote-plugins/sigint/status"><img src="https://agentmods.dev/badge/commands/zircote-plugins/sigint/status.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.00007 | $0.00942 |
| Opus 5.5 | $0.00003 | $0.00377 |
| Sonnet 5.5 | $0.00001 | $0.00188 |
| Haiku 4.5 | $0.00001 | $0.00094 |
Grade A, and why
status 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.
What it actually says
Display the current sigint research session status and progress.
Arguments:
--verbose- Show detailed findings and sources
Process:
-
Find active research session: Read
sigint.config.jsontopics as the primary session index (comprehension-only — Read is acceptable per Structured Data Protocol). List all topics with theirstatus,dimensions,updated, andfindings_count.Fall back to scanning
./reports/*/state.jsononly ifsigint.config.jsonhas no topic entries (legacy sessions predating topic registration). -
Load session state (comprehension-only — Read is acceptable per Structured Data Protocol): Read state.json and parse:
- Topic and scope
- Current phase
- Findings count by category
- Sources count
- Last activity
-
Calculate progress metrics:
- Research completeness (based on methodology coverage)
- Data freshness (age of newest finding)
- Coverage gaps (areas not yet researched)
-
Display status dashboard:
╔══════════════════════════════════════════════════════════╗ ║ SIGINT Research Status ║ ╠══════════════════════════════════════════════════════════╣ ║ Topic: [research topic] ║ ║ Phase: [discovery | analysis | synthesis] ║ ║ Started: [date] | Last Updated: [date] ║ ╠══════════════════════════════════════════════════════════╣ ║ FINDINGS ║ ║ ├─ Market Overview: [✓ | ○ | ─] ║ ║ ├─ Competitive: [✓ | ○ | ─] ║ ║ ├─ Market Sizing: [✓ | ○ | ─] ║ ║ ├─ Trends: [✓ | ○ | ─] ║ ║ ├─ Customer Research: [✓ | ○ | ─] ║ ║ ├─ Tech Assessment: [✓ | ○ | ─] ║ ║ ├─ Financial: [✓ | ○ | ─] ║ ║ └─ Regulatory: [✓ | ○ | ─] ║ ╠══════════════════════════════════════════════════════════╣ ║ TEAM STATUS (if active) ║ ║ ├─ competitive: [✓ complete | ⟳ in_progress | ─] ║ ║ ├─ sizing: [✓ complete | ⟳ in_progress | ─] ║ ║ └─ trends: [✓ complete | ⟳ in_progress | ─] ║ ╠══════════════════════════════════════════════════════════╣ ║ Sources: [count] | Findings: [count] ║ ║ Freshness: [days since last update] ║ ╠══════════════════════════════════════════════════════════╣ ║ NEXT STEPS ║ ║ • [suggested action 1] ║ ║ • [suggested action 2] ║ ╚══════════════════════════════════════════════════════════╝Legend: ✓ = complete, ○ = in progress, ─ = not started
-
If
--verbose: Show list of all findings with summaries. Show list of all sources. Show current trend indicators (INC/DEC/CONST). -
Suggest next actions: Based on coverage gaps and phase:
- Missing areas → suggest
/sigint:augment [area] - All areas covered → suggest
/sigint:report - Stale data → suggest
/sigint:update
- Missing areas → suggest
Output:
- Visual status dashboard
- Progress indicators
- Suggested next steps
Example usage:
/sigint:status
/sigint:status --verbose
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 · 88 lines · 7 tokens per session scan A 9325a51bc1f3
status is a command published in the GitHub repository zircote-plugins/sigint (24 stars, last pushed 2mo ago), licensed MIT. It adds 7 tokens to every session and 942 once invoked, about $0.0000 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 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.
community-building-strategist
Comprehensive community building strategy including platform selection, channel structure, member journey mapping, engagement ladder tactics, community programming rituals, moderation guidelines, launch plan, growth strategy, and success metrics for building thriving online communities.
business-model-designer
Complete Business Model Canvas design with all 9 blocks analyzed. Transforms validated ideas into viable business models with revenue clarity and operational strategy.
email-marketing-architect
Comprehensive email marketing strategy including drip campaigns, segmentation, automation workflows, copywriting guidelines, deliverability best practices, and 90-day implementation roadmap with full-funnel lifecycle coverage.