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 skills/zircote-plugins/sigint/augmentWrote 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/skills/zircote-plugins/sigint/augment)<a href="https://agentmods.dev/skills/zircote-plugins/sigint/augment"><img src="https://agentmods.dev/badge/skills/zircote-plugins/sigint/augment/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/skills/zircote-plugins/sigint/augment"><img src="https://agentmods.dev/badge/skills/zircote-plugins/sigint/augment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00053 | $0.03037 |
| Opus 5.5 | $0.00021 | $0.01215 |
| Sonnet 5.5 | $0.00011 | $0.00607 |
| Haiku 4.5 | $0.00005 | $0.00304 |
Grade A, and why
augment 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 — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sigint Augment Skill (Swarm Orchestration)
You are the team lead for a focused research augmentation session. You spawn ONE dimension-analyst teammate, wait for results via SendMessage, generate scenario graphs if applicable, and update the research state.
Structured Data Protocol: All JSON file mutations MUST follow protocols/STRUCTURED-DATA.md. Use jq via Bash for state.json updates. Every write or mutation MUST be followed by schema validation using schemas/state.jq — 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.
Arguments parsed from $ARGUMENTS:
Input sanitization: truncate $ARGUMENTS to 200 characters total, strip backticks and angle brackets.
$1— area to investigate (e.g., "competitor pricing", "regulatory landscape")--dimension <type>(alias:--methodology) — optional: competitive, sizing, trends, customer, tech, financial, regulatory, trend_modeling
Phase 0: Pre-flight + Initialize
Step 0.1: Resolve active research session
-
Find the active research state file:
Glob("./reports/*/state.json")- If multiple exist: use
AskUserQuestionto ask which topic to augment. - If none exist: respond "No active research session found. Run /sigint:start first." and stop.
- If multiple exist: use
-
Read the state file. Extract:
topic— human-readable topic nametopic_slug— slug identifier (derive if missing:topic.toLowerCase().replace(/[^a-z0-9]+/g,'-').slice(0,40))elicitation— full elicitation context
Step 0.2: Identify methodology
Map area to dimension and skill directory:
| Area keywords | Dimension | Skill Dir |
|---|---|---|
| competitor, competitive, market players, positioning | competitive | competitive-analysis |
| size, TAM, SAM, SOM, opportunity, market size | sizing | market-sizing |
| trend, pattern, future, forecast, scenario | trends | trend-analysis |
| user, customer, persona, buyer, segment | customer | customer-research |
| technology, tech, feasibility, stack, build vs buy | tech | tech-assessment |
| revenue, economics, pricing, unit economics, SaaS | financial | financial-analysis |
| compliance, regulatory, legal, privacy, GDPR | regulatory | regulatory-review |
| scenario, causal model, three-valued logic, trade-offs | trend_modeling | trend-modeling |
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.
- 1mo ago First seen · 314 lines · 53 tokens per session scan A 2a847a1bbb26
augment is a skill published in the GitHub repository zircote-plugins/sigint (24 stars, last pushed 2mo ago), licensed MIT. It adds 53 tokens to every session and 3,037 once invoked, about $0.0002 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 skills, from other repositories
gr-competitor
A competitor research workflow that collects information from rival websites, including landing pages, pricing, blogs, and past changes. Wayback refers to the Internet Archive’s record of older versions of websites.
radar-publish-council
Publishes the Strategic War Room addendum from /radar-council to all three surfaces. Appends the addendum to the local briefing markdown, fills the warroom section of the dashboard data and re-renders the dashboard, and appends the addendum to the Notion briefing page while checking its War Room box. Use after the…
executive-market-research
Generate executive-grade market research reports - full (35-45 pages) or Executive Brief (8-10 pages, quick mode) - for any product, sector or country. Triangulated sources from UN Comtrade, World Bank, IMF, EIU. Outputs PDF + interactive HTML in English, Arabic (RTL), or French. Use for market sizing (TAM/SAM/SOM)…
radar-onboard
Run this FIRST, before any other radar skill. Sets up Competitive Intelligence Radar by ASKING whether BrightData and Notion are connected, live-testing one real call to each, detecting which MCP prefix is actually live, and writing radar.config.json with the user's business context. Use when the user runs…
radar-provision-notion
Creates the two Notion databases (Competitors and Briefings) the radar publishes to, but ONLY after SHOWING the proposed schema and getting the user's explicit approval. Use during /radar-setup after onboarding, or when radar-publish-notion reports the databases are missing. Idempotent: if the databases already exist…
radar-publish-notion
Publishes the run to Notion. Upserts one row per competitor in the Competitors database (matched by domain, with a Change field for week-over-week tracking) and creates a Briefings page holding the full briefing. Use after radar-merge-briefing. Requires the databases to exist (radar-provision-notion). Writing rows to…