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 chadcorp/warden --skill idea-scoutgit clone --depth 1 https://github.com/chadcorp/wardenWrote 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/chadcorp/warden/idea-scout)<a href="https://agentmods.dev/skills/chadcorp/warden/idea-scout"><img src="https://agentmods.dev/badge/skills/chadcorp/warden/idea-scout.svg" alt="Measured on agentmods" 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.00000 | $0.00546 |
| Opus 5 | $0.00000 | $0.00273 |
| Sonnet 5 | $0.00000 | $0.00109 |
| Haiku 4.5 | $0.00000 | $0.00055 |
Grade A, and why
idea-scout 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 7d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Idea Scout
Find and rigorously score a net-new idea before building, so you don't pour effort into something nobody wants. This is a reasoning protocol, not a tool: it needs no network, no files, and no secrets — only disciplined thinking.
When to use
"What should I build next?", "Is this idea worth it?", "Score this idea", "Will this sell?", or any moment you are tempted to start building on a hunch.
The protocol
-
Frame the buyer and the pain. Name one specific buyer and the recurring, expensive, already-funded pain they feel. Vague audiences ("everyone") fail this step. Write the pain as a sentence the buyer would say out loud.
-
Demand evidence, not vibes. List concrete signals the demand is real: existing paid alternatives, search/community volume, repeated complaints, money already changing hands. An idea with zero external evidence scores low no matter how clever it feels.
-
Score on a rubric with anti-inflation ceilings. Rate each dimension 1–6 and cap optimism:
- Pain intensity, Buyer reachability, Willingness to pay, Differentiation, Build feasibility, Competition headroom, Durability, Distribution fit.
- A dimension only scores high with stated evidence. No evidence → ≤ 3.
-
Blind-scout convergence. Generate two or three independent takes on the same space without letting them see each other, then keep only ideas that more than one scout surfaces. Convergence beats a single confident guess.
-
Mandatory pre-mortem. Assume it failed a year from now. Write the three most likely reasons. If the top reason is fatal and unfixable, stop here.
-
Define the cheapest possible test. State the smallest artifact or signal that would validate or kill the idea this week (a landing page, a waitlist target, five real conversations). Name a pass/fail number before running it.
Output
A one-page verdict: buyer + pain, evidence list, rubric table with total,
the pre-mortem's top risk, and the cheap test with its pass/fail bar. End with
a clear BUILD / DON'T BUILD / TEST FIRST call. Hand a BUILD verdict to
build-brain/build-product.
What ships with it
3 files 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.
- 7d ago First seen · 48 lines · 0 tokens per session scan A 99e5c4fc975e
idea-scout is a skill published in the GitHub repository chadcorp/warden (0 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 546 tokens. 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-31.
Other skills, from other repositories
test-skill
Extended diagnostic skill that validates the full Cognithor skill lifecycle — SkillRegistry scanning, keyword matching (exact + fuzzy at 70% threshold), and async execution. Use when testing skill discovery, debugging keyword matching accuracy, validating the SkillRegistry scan cycle, or verifying async execute()…
wetter-abfrage
Weather query skill that retrieves current temperature, humidity, wind speed, and multi-day forecasts for a given city or coordinate. Use when checking the weather, getting a forecast, looking up temperature or wind conditions, or planning outdoor activities based on weather data.
code-review
Performs structured code review on a file or directory.
backup
Automated hourly backup skill that creates timestamped archives of Cognithor config files, skill definitions, and data directories on a cron schedule. Use when setting up automated backups, restoring from snapshots, scheduling data protection, or configuring backup retention policies.
gmail-sync
API integration skill that fetches Gmail messages, syncs inbox labels, and processes attachments via the Gmail REST API. Use when fetching new emails, syncing inbox state, triaging unread messages, exporting mail data, or integrating Gmail into automated workflows.
forkmind-archivist
Use when conversation context should be saved and then removed from the live model window — context is getting full, a sub-topic is finished, a large file dump or tool transcript is done being useful, or the user says "offload my context", "save this conversation and clear it", "archive this as a DAG", "restore that…