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/Infrasity-Labs/dev-gtm-claude-skillsnpx agentmods add skills/infrasity-labs/dev-gtm-claude-skills/blog-discourseWrote 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/infrasity-labs/dev-gtm-claude-skills/blog-discourse)<a href="https://agentmods.dev/skills/infrasity-labs/dev-gtm-claude-skills/blog-discourse"><img src="https://agentmods.dev/badge/skills/infrasity-labs/dev-gtm-claude-skills/blog-discourse/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/infrasity-labs/dev-gtm-claude-skills/blog-discourse"><img src="https://agentmods.dev/badge/skills/infrasity-labs/dev-gtm-claude-skills/blog-discourse.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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 Agent Snooping · line 104 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Excessive Agency · line 108 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00168 | $0.03126 |
| Opus 5 | $0.00084 | $0.01563 |
| Sonnet 5 | $0.00034 | $0.00625 |
| Haiku 4.5 | $0.00017 | $0.00313 |
Grade A, and why
blog-discourse 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 9d 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blog Discourse: Real Discourse Research, API-Free
blog-discourse is the recency + engagement lens that blog-researcher (authority-first) lacks. It asks: in the last 30 days, what are practitioners and customers actually saying about this topic on the public web?
This sub-skill uses WebSearch with platform-targeted site operators. No API keys required.
Commands
| Command | Purpose |
|---|---|
/blog discourse <topic> |
Produce a discourse brief at project-root DISCOURSE.md |
/blog discourse <topic> --days 90 |
Widen the freshness window from 30 to 90 days |
/blog discourse <topic> --feed-into brief |
Run the brief, then immediately invoke /blog brief <topic> with DISCOURSE.md auto-loaded |
/blog discourse <topic> --feed-into write |
Run the brief, then invoke /blog write <topic> |
/blog discourse <topic> --feed-into strategy |
Run the brief, then invoke /blog strategy <topic> |
/blog discourse <topic> --input results.json |
Skip search; build the brief from a pre-gathered results file. The flag name matches scripts/discourse_research.py --input directly. |
Workflow
Phase 0: Topic Pre-Flight (mandatory)
Before any search, run the four keyword-trap checks from skills/blog/references/research-quality.md (Class 1 demographic shopping, Class 2 numeric trap, Class 3 overly-literal phrase, Class 4 generic single-noun). If the topic matches a class:
- Emit a single one-line note:
Pre-Flight: matched Class N. Action: <reframe or clarifying question>. - If the action is a clarifying question, STOP and wait for the user.
- If the action is a reframe, proceed with the reframed query and document the reframe in the brief.
Running discourse research on a trap topic wastes WebSearch calls and produces noise.
Phase 1: Topic Decomposition (Step 0.55)
For named-entity topics, decompose into discrete searchable queries. Use the checklist from research-quality.md:
- Primary entity (official statements, vendor site)
- Counter-perspective (critics, competitors, contrarians)
- Practitioner discourse (subreddits, forums, dev.to, Medium)
- Tangential entities (founder, parent org, related products)
- Time anchor (last 30 or 90 days)
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.
- 9d ago First seen · 222 lines · 168 tokens per session scan A 96192c72168a
blog-discourse is a skill published in the GitHub repository Infrasity-Labs/dev-gtm-claude-skills (124 stars, last pushed 2mo ago), licensed MIT. It adds 168 tokens to every session and 3,126 once invoked, about $0.0008 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-09-03.
Other skills, from other repositories
geo-audit
Full website GEO+SEO audit with parallel subagent delegation. Orchestrates a comprehensive Generative Engine Optimization audit across AI citability, platform analysis, technical infrastructure, content quality, and schema markup. Produces a composite GEO Score (0-100) with prioritized action plan.
geo
GEO-first SEO analysis tool. Optimizes websites for AI-powered search engines (ChatGPT, Claude, Perplexity, Gemini, Google AI Overviews) while maintaining traditional SEO foundations. Performs full GEO audits, citability scoring, AI crawler analysis, llms.txt generation, brand mention scanning, platform-specific…
geo-brand-mentions
Brand mention and authority scanner for AI visibility. Analyzes brand presence across platforms that AI models rely on for entity recognition and citation decisions. Produces a Brand Authority Score (0-100) with platform-specific recommendations.
geo-llmstxt
Analyzes and generates llms.txt files -- the emerging standard for helping AI systems understand website structure and content. Can validate existing llms.txt files or generate new ones from scratch by crawling the site.
agent-readiness-scan
Use when a client audit, GEO/AI-visibility snapshot, or remediation re-scan needs the Cloudflare agent-readiness score from isitagentready.com — e.g. Theo client audits, "is the site agent-ready", markdown negotiation / MCP / llms.txt / Content-Signal checks, or tracking score deltas after Tier 0/1 fixes.
found-by-ai
Measure whether AI engines actually recommend a business when buyers ask. Runs the free live scan at areyoufoundbyai.com (no auth, 60s), reads the verdict and the rivals AI names instead, hands back the fix plan, and wires monitored sites into a fix-and-re-measure loop over MCP.