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 skills/zircote-plugins/sigint/issuesnpx skills add zircote-plugins/sigint --skill 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.00058 | $0.02451 |
| Opus 5 | $0.00029 | $0.01226 |
| Sonnet 5 | $0.00012 | $0.00490 |
| Haiku 4.5 | $0.00006 | $0.00245 |
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 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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sigint Issues Skill (Swarm Orchestration)
You are the team lead orchestrating GitHub issue creation from research findings. You spawn the issue-architect agent as a persistent teammate, wait for its completion signal, then present results and clean up the team.
MANDATORY SWARM ORCHESTRATION — DO NOT USE PLAIN AGENT SPAWNS
You MUST use the full swarm pattern: TeamCreate → TaskCreate → Agent(team_name) → SendMessage. Do NOT fall back to standalone Agent(subagent_type=...) without a team. The swarm pattern enables persistent teammates that coordinate via shared task lists and messaging.
Phase 0: Parse Arguments and Initialize
Step 0.1: Parse Arguments
Extract from $ARGUMENTS. Input sanitization: truncate $ARGUMENTS to 200 characters total, strip backticks and angle brackets.
--repo <owner/repo>→repo(default: detect from git remote or state.json config). Validate format: must match[a-zA-Z0-9._-]+/[a-zA-Z0-9._-]+. Reject values containing shell metacharacters, spaces, or path traversal sequences.--dry-run→dry_run = true(preview only, do not create issues)--labels <list>→labels(comma-separated, default: empty). Each label must be a non-empty string; strip whitespace around commas.
Remaining text after flags is ignored for issues (no positional argument).
Step 0.2: Find Active Research Session
Scan ./reports/*/state.json for sessions with status: "active". If multiple exist, load the most recently updated (compare started or file mtime). Extract:
topic— human-readable topic nametopic_slug— directory nameelicitation— full elicitation object for issue prioritization
If no active session found, error: "No active research session. Run /sigint:start <topic> first."
Resolve reports_dir from config (REQUIRED — do not hardcode paths):
REPORTS_DIR=$(jq -r --arg slug "$TOPIC_SLUG" '.topics[$slug].reports_dir // "./reports/\($slug)"' sigint.config.json 2>/dev/null || echo "./reports/$TOPIC_SLUG")
All subsequent path references MUST use {reports_dir} instead of ./reports/{topic_slug}/.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 259 lines · 58 tokens per session scan A 241ace3b6040
issues is a skill published in the GitHub repository zircote-plugins/sigint (20 stars, last pushed 15d ago), licensed MIT. It adds 58 tokens to every session and 2,451 once invoked, about $0.0003 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 skills, from other repositories
gr-competitor
竞品深度扫描。批量抓取对手落地页（title/h1/intro/pricing）、定价页、博客 top 10、 变更历史（Wayback）。底层调 actionbook（并发 30 tab + 省 90% token）。 当用户说"分析对手"、"看看竞品在做啥"、"找对标"、"扫一下 top 10"时调用。.
startup-design
Design, validate, and plan a startup from scratch. Covers market research, competitive analysis, business model, brand identity, product definition, financial projections, and validation experiments. Trigger when the user has a startup idea to explore, wants to validate a business concept, needs a business plan or…
startup-pitch
Build investor-ready pitch scripts in multiple formats (10-min, 5-min, 2-min, 1-min elevator, investor email). Produces pitch narratives, Q&A preparation, pitch scoring rubric, and optional investor roleplay practice. Use when the user wants to create a pitch, prepare for investor meetings, craft a startup pitch…
startup-competitors
Deep competitive intelligence for any market. Analyzes competitors' products, pricing, customer sentiment, GTM strategy, and growth signals using real web data. Produces battle cards, pricing landscape, and feature matrix. Use when the user wants to understand their competitive landscape, analyze competitors, compare…
startup-positioning
Market positioning strategy using the April Dunford framework, enriched with JTBD discovery, Moore positioning statement, and Neumeier's Onliness Test. Produces a complete positioning document, positioning statement, competitive alternatives map, and market category analysis. Use when the user wants to define or…
mapping-markets
Map the market around any company from its domain alone — competitors, substitutes, the infrastructure it sits on, the directories that list it, the publications that cover it and the communities its buyers argue in — with a source and a reason on every entry. Use this skill whenever someone wants a competitive…