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 Freespirits/social-auto-engine --skill niche-researchgit clone --depth 1 https://github.com/Freespirits/social-auto-engineWrote 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/freespirits/social-auto-engine/niche-research)<a href="https://agentmods.dev/skills/freespirits/social-auto-engine/niche-research"><img src="https://agentmods.dev/badge/skills/freespirits/social-auto-engine/niche-research/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/freespirits/social-auto-engine/niche-research"><img src="https://agentmods.dev/badge/skills/freespirits/social-auto-engine/niche-research.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.00111 | $0.01147 |
| Opus 5 | $0.00056 | $0.00574 |
| Sonnet 5 | $0.00022 | $0.00229 |
| Haiku 4.5 | $0.00011 | $0.00115 |
Grade A, and why
niche-research 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.
This is a copy
100% identical to niche-research — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Niche Research
CRITICAL: Auto-start on load
When this skill triggers, go straight to Step 1. Do not summarise the research method.
Prerequisites
This skill needs live browsing. Use this order of preference:
- Claude for Chrome extension (preferred). Check that the extension is enabled and Claude has permission to browse on the current tab. If not, tell the user:
Enable the Claude for Chrome extension and open a blank tab. I need to drive the browser to scroll Reddit, X, and run Google searches with verified dates.
- Playwright MCP as a fallback if the Claude for Chrome extension is not available.
- WebSearch + WebFetch tools as a last resort (less thorough on feed scrolling).
Pick the best available path and continue.
Step 1. Gather the niche
Call AskUserQuestion:
[
{
"question": "What niche do you want to research?",
"header": "Niche",
"multiSelect": false,
"options": [
{"label": "I will type my niche", "description": "Type the exact niche phrase after this"},
{"label": "Pull from about-me.md", "description": "Use the niche and audience already in my voice files"}
]
}
]
If the user picks "Pull from about-me.md", read the file from the project root. If the file does not exist or does not name a clear niche, fall back to asking the user to type it.
Step 2. Browse like a human researcher
Drive the browser through these actions in order. Verify publish dates on every item. Exclude anything older than 7 days from today without exception.
2a. Reddit feed scanning
- Navigate to https://www.reddit.com/ (home feed).
- Scroll the feed. Load more posts.
- Open niche-relevant posts. On each post, check the "posted X days ago" timestamp.
- Discard posts older than 7 days.
- Repeat with https://www.reddit.com/r/popular/.
- Also search any niche-specific subreddits that come up while scrolling.
2b. X (Twitter) feed scanning
- Navigate to https://x.com/home (For You feed).
- Scroll multiple screens.
- Open full threads for niche-relevant tweets.
- Check the post timestamp on each thread.
- Discard posts older than 7 days, even if engagement is high.
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 · 127 lines · 111 tokens per session scan A 18595b0aa62b
niche-research is a skill published in the GitHub repository Freespirits/social-auto-engine (25 stars, last pushed 1mo ago), licensed MIT. It adds 111 tokens to every session and 1,147 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to niche-research, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
mcp-host-styling-integration
Integrates MCP App UI with host theming system. Applies host CSS variables, handles onhostcontextchanged, safe area insets, display mode detection, and fullscreen configuration.
cog-knowledge-consolidation
Build structured knowledge frameworks from scattered vault notes with source attribution.
context-engineering
Dynamic context injection, mode switching (dev/review/research), selective loading, and strategic compaction for token optimization.
plan-implementation
Disciplined execution of approved plans with step-by-step verification, phase checkpoints, failure investigation, and mandatory code/security reviews.
security-review
Security vulnerability assessment identifying OWASP risks, injection vectors, authentication issues, and data exposure with severity classification.
consensus-mechanisms
Multi-protocol consensus for agent swarms supporting Raft leader election, Byzantine fault tolerance, Gossip state propagation, and CRDT conflict-free merging.