Borrowing it
Nothing to install: this file belongs to ashishpatill/tell-proof. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ashishpatill/tell-proof/master/.cursor/skills/surface-recipe-map/SKILL.mdgit 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/surface-recipe-map)<a href="https://agentmods.dev/skills/ashishpatill/tell-proof/surface-recipe-map"><img src="https://agentmods.dev/badge/skills/ashishpatill/tell-proof/surface-recipe-map/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/surface-recipe-map"><img src="https://agentmods.dev/badge/skills/ashishpatill/tell-proof/surface-recipe-map.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.00047 | $0.00098 |
| Opus 5.5 | $0.00019 | $0.00039 |
| Sonnet 5.5 | $0.00009 | $0.00020 |
| Haiku 4.5 | $0.00005 | $0.00010 |
Grade A, and why
surface-recipe-map 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
surface-recipe-map
Full playbook: agent-skills/web-design/premium-content-custom-web/surface-recipe-map/SKILL.md
Coverage table: agent-skills/web-design/COVERAGE.md
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 · 11 lines · 47 tokens per session scan A b9a10a328721
surface-recipe-map is a skill published in the GitHub repository ashishpatill/tell-proof (2 stars, last pushed 22d ago), licensed MIT. It adds 47 tokens to every session and 98 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
orchestrate-package
Orchestrate final packaging. Checks the repo against the exact submission rules in problemstatement.md (output.csv header, row coverage, allowed values, code, README, transcript, secrets) and only then builds the submission/ folder with output.csv, code.zip, README, transcript and usage report. Use in the final hours…
orchestrate-test-fix
Orchestrate phases 3 and 4 - find where the built agent is wrong or fragile (edge cases, overfitting, determinism, two-strategy comparison, one-input trace), then fix wrong rows one change at a time with a diff of the whole output. Use once the pipeline runs on the sample, and whenever output rows are wrong or weakly…
orchestrate-submit
Orchestrate phases 5 and 6 - self-score all four sections against the rubric, harden security and robustness, check cost numbers, then run the spec audit, consistency check and release gate before packaging the submission. Use once the output is stable, and in the final two hours before submitting.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
writing-livekit-scenarios
Creates and maintains the scenarios a LiveKit agent simulation runs, and wires the agent to consume them. Use when the user asks "what should I test", "generate simulation scenarios", "write scenarios for my agent", "add a scenario for X", "organize my scenario files", "my simulations are flaky", "the scenario hits my…
running-livekit-simulations
Runs LiveKit agent simulations and acts on the results. Use when the user says "run my simulations", "regression test my agent before deploying", "run the scenarios", "use lk agent simulate", "did my agent pass", "why did this scenario fail", "run simulations in CI", "test the audio pipeline", "check turn-taking and…