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 agentmods add skills/mathews-tom/armory/idea-validatornpx skills add Mathews-Tom/armory --skill idea-validatorgit clone --depth 1 https://github.com/Mathews-Tom/armoryWrote 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/mathews-tom/armory/idea-validator)<a href="https://agentmods.dev/skills/mathews-tom/armory/idea-validator"><img src="https://agentmods.dev/badge/skills/mathews-tom/armory/idea-validator.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 | $0.00077 | $0.02350 |
| Opus 5 | $0.00039 | $0.01175 |
| Sonnet 5 | $0.00015 | $0.00470 |
| Haiku 4.5 | $0.00008 | $0.00235 |
Grade A, and why
idea-validator 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 4d 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Business Idea Validator
Purpose
Perform rigorous, multi-dimensional validation of business ideas by orchestrating parallel research and synthesizing findings into a scored, actionable report. The goal is honest assessment — surfacing what holds up under scrutiny and what does not — rather than cheerleading or reflexive dismissal.
Phase 1: Input Intake & Classification
Classify the input:
| Input Type | Indicators | Adaptation |
|---|---|---|
| Elevator pitch | 1-3 sentences, informal | Extract hypothesis, ask for missing details |
| Business plan | Structured, multiple sections | Validate claims against research |
| Feature proposal | Technical focus, existing product context | Narrow scope to feature viability |
| Repo/codebase | File paths, code references | Technical feasibility + market fit |
| Pivot assessment | "Should we pivot to...", comparison context | Compare current vs proposed direction |
Extract core elements from the input:
- Problem statement — what pain point exists
- Proposed solution — how it addresses the pain
- Target customer — who experiences this problem
- Value proposition — why this solution over alternatives
- Revenue model — how it generates money
If any core element is missing or ambiguous, ask clarifying questions. Cap at 5 questions. Do not proceed with fabricated assumptions for missing elements — get real answers.
Phase 2: Lean Canvas Construction
Build a complete Lean Canvas using references/lean-canvas.md as the framework guide.
Populate all 9 boxes:
- Problem — top 3 problems the customer faces
- Customer Segments — target market + early adopter profile
- Unique Value Proposition — single clear compelling message
- Solution — top 3 features addressing the top 3 problems
- Channels — path to reaching customers
- Revenue Streams — pricing model and revenue mechanics
- Cost Structure — fixed and variable costs
- Key Metrics — what to measure for progress
- Unfair Advantage — what cannot be easily copied or bought
What ships with it
5 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.
- 4d ago First seen · 224 lines · 77 tokens per session scan A 2fdeb46ffac1
idea-validator is a skill published in the GitHub repository Mathews-Tom/armory (316 stars, last pushed 6d ago), licensed MIT. It adds 77 tokens to every session and 2,350 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
manager
Sync session work into GitHub issues, or query track status across repos. Write: find/update issue + W-label. Read: "что по ". Triggers: "создай issue", "синкни сессию", "manager". Not day/week plans (daily-tasks).
weekly-retro
Use when the user is closing an ISO week, reviewing planned outcomes against evidence, interviewing work Areas, resolving unfinished commitments, or asking for "ретро", "weekly retro", "week review", or lessons from the week.
art-director
Orchestrate iterative visual style searches with branch prompts, decision graphs, feedback loops, and final direction selection.
corp-doctor
Use when a Personal Corp operating loop needs setup, repair, a new department, or task routing: HQ files and agent rules, GitHub issue workflow, corp- owner map, department repositories, or deciding which repo an issue belongs to. Triggers: "corp doctor", "почини контур", "заведи отдел", "куда положить задачу"…
html-draft
Use when user wants a standalone HTML diagram in flat engineering blueprint style — architecture diagrams, system flows, technical spec sheets, component maps. Generates one HTML file using Tailwind v4 (browser CDN) for layout and D3 v7 (CDN) for SVG diagrams. User-invoked only — do NOT auto-trigger. Triggers on…
idea
Use when capturing ONE new idea the user voices and wants recorded — "save this idea", "I have an idea", "log this idea", "/idea", "idea: ...". Creates a provenance-tracked folder (one folder per idea) in your ideas repo, dedups against an index, optionally mirrors to a GitHub Project view filtered by label:idea. NOT…