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 skills add zircote-plugins/sigint --skill issuesgit 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/skills/zircote-plugins/sigint/issues)<a href="https://agentmods.dev/skills/zircote-plugins/sigint/issues"><img src="https://agentmods.dev/badge/skills/zircote-plugins/sigint/issues/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/issues"><img src="https://agentmods.dev/badge/skills/zircote-plugins/sigint/issues.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 97 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00058 | $0.02451 |
| Opus 5.5 | $0.00023 | $0.00980 |
| Sonnet 5.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 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 — 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.
- 1mo ago First seen · 259 lines · 58 tokens per session scan A 241ace3b6040
issues is a skill published in the GitHub repository zircote-plugins/sigint (24 stars, last pushed 2mo ago), licensed MIT. It adds 58 tokens to every session and 2,451 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.
pm-prd
Assemble a full, market-driven Product Requirements Document (PRD) the Pragmatic way — problem-before-solution, evidence-based, persona-first. Use when the PM asks for a PRD, product spec, feature doc, "write the requirements doc", or "put it all together for the team". Pulls in existing personas, positioning, market…
pm-product-canvas
Build a Pragmatic Institute Product Canvas / business case to justify investing in an opportunity — the market-driven way. Use when the PM asks to "make the business case", "justify this to leadership", "size the market", "should we buy, build or partner", "what's the ROI", "build a product canvas", or "get buy-in for…
pm-gap-analysis
Run a Pragmatic Institute Gap Analysis — a market-driven self-assessment of how well the team performs the 37 activities of the Pragmatic Framework, who owns each, and where the biggest gaps are. Use when the PM asks "where do we stand", "how are we doing on the framework", a product-org self-assessment, a maturity…
pm-opportunity-scoring
Score and rank product opportunities objectively with the Pragmatic Institute Opportunity Scoring model — across distinctive competency fit, competitive landscape, investment level, and impact to buyers/users. Use when the PM asks which idea to pursue, "score these opportunities", prioritize projects/bets, or compare…
pm-product-roadmap
Build a Pragmatic Institute Product Roadmap that communicates vision, direction and priorities over time — a plan, not a commitment. Use when the PM asks for a "roadmap", "product vision", "what's coming", "phases", "themes over time", or wants to align stakeholders on direction (as distinct from a dated release…