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 fzfclee/consulting-skills --skill validation-plangit clone --depth 1 https://github.com/fzfclee/consulting-skillsWrote 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/fzfclee/consulting-skills/validation-plan)<a href="https://agentmods.dev/skills/fzfclee/consulting-skills/validation-plan"><img src="https://agentmods.dev/badge/skills/fzfclee/consulting-skills/validation-plan.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.00051 | $0.00735 |
| Opus 5 | $0.00026 | $0.00367 |
| Sonnet 5 | $0.00010 | $0.00147 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
validation-plan 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 8d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validation Plan
Use this skill to turn a recommendation into a testable plan with evidence standards and decision gates.
Method Notes
- Validation is not the same as implementation. It defines what evidence will increase or reduce confidence.
- A good validation plan names the hypothesis, test, signal, threshold, owner, timing, and decision rule.
- It should be proportional to risk: higher-risk decisions need stronger validation.
Required Inputs
Collect or infer these inputs before execution:
- recommendation or hypothesis to validate
- decision consequence and risk level
- available evidence and current confidence
- feasible tests or evidence sources
- timeline, owner, and decision deadline
If an input is missing, mark it as missing, state the assumption used, and add a validation action.
When Not To Use
Do not use when the user has not yet formed a hypothesis or action option. Use evidence-map, issue-tree, or hypothesis-tree first.
Step-by-Step Execution
| Step | Required input | How to execute | Output |
|---|---|---|---|
| State the hypothesis | Recommendation, expected outcome, current confidence. | Write the claim to be validated in one testable sentence. | Validation hypothesis. |
| Define decision consequence | Risk, reversibility, cost of wrong action. | Decide how strong the evidence must be before action. | Evidence standard. |
| Select validation method | Evidence sources, access, timeline. | Choose interview, document check, commitment test, pilot, prototype, data analysis, stakeholder signal, or market test. | Validation method. |
| Define success and failure signals | Hypothesis, expected behavior, thresholds. | Make pass, adjust, and stop criteria explicit. | Decision criteria. |
| Plan execution | Owner, timing, script or data need, dependencies. | Specify who does what by when and with what artifact. | Validation workplan. |
| Decide next gate | Test result, action options. | Define what decision will be made after evidence arrives. | Continue / adjust / stop gate. |
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.
- 8d ago First seen · 80 lines · 51 tokens per session scan A 33e0832f4eb3
validation-plan is a skill published in the GitHub repository fzfclee/consulting-skills (4 stars, last pushed 20d ago), licensed Apache-2.0. It adds 51 tokens to every session and 735 once invoked, about $0.0003 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-31.
Other skills, from other repositories
taxue-career-resume
A resume and job-description tool for comparing a person’s experience with a specific job opening. It can create a reusable master resume and tailored versions for individual applications.
taxue-industry
A three-level method for understanding an industry: a broad overview, deeper research, and business judgement. It examines the supply chain, competitors, and market structure.
taxue-solve
A thinking aid that turns a vague problem or difficult choice into a clear plan of action. It first examines what the real problem is, including whether emotions are hiding the main question.
taxue
A main entry point for a decision-support system that asks questions, clarifies what you really need, and guides you toward an action.
meme-interpreter
An internet-meme and slang interpreter that explains online jokes, expressions, images, group jargon, and references in their real social context.
taxue-business
A business-opportunity assessment guide for judging whether an idea, project, business model, side project, or way to make money is worth pursuing.