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 ashishpatill/tell-proof --skill analyze-features-requirementsgit clone --depth 1 https://github.com/ashishpatill/tell-proofWrote 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/ashishpatill/tell-proof/analyze-features-requirements)<a href="https://agentmods.dev/skills/ashishpatill/tell-proof/analyze-features-requirements"><img src="https://agentmods.dev/badge/skills/ashishpatill/tell-proof/analyze-features-requirements/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/ashishpatill/tell-proof/analyze-features-requirements"><img src="https://agentmods.dev/badge/skills/ashishpatill/tell-proof/analyze-features-requirements.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.00021 | $0.00120 |
| Opus 5.5 | $0.00008 | $0.00048 |
| Sonnet 5.5 | $0.00004 | $0.00024 |
| Haiku 4.5 | $0.00002 | $0.00012 |
Grade A, and why
analyze-features-requirements 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 1mo 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.
What it actually says
analyze-features-requirements
Extract product features, audience, business goal, and constraints.
Output
- Prioritized feature list (p0/p1/p2)
- Inferred site kind: saas-marketing | dashboard-webapp | corporate-story | docs-educational
- Recommended section order
- Goals list tied to buyer outcomes
Rules
- Never invent features not supplied
- Map each p0 feature into hero and primary sections
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.
- 1mo ago First seen · 19 lines · 21 tokens per session scan A fc69dd737355
analyze-features-requirements is a skill published in the GitHub repository ashishpatill/tell-proof (2 stars, last pushed 11d ago), licensed MIT. It adds 21 tokens to every session and 120 once invoked, about $0.0001 per session on Opus 5.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
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
track-management
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
contact-cache
Track all identified/contacted people across strategies. CSV-backed contact database with dedup by LinkedIn URL or email. Prevents duplicate outreach when running strategies on a recurring cadence.
feedback-page-generator
Deprecated compatibility entry for Feedback Page construction. This page is now maintained in Pagina; install and use page-builder to build a new Feedback Page.
feature-decision
Framework for making feature prioritization decisions.