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 d-mariano/spicyclaude --skill feasibility-cold-readgit clone --depth 1 https://github.com/d-mariano/spicyclaudeWrote 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/d-mariano/spicyclaude/feasibility-cold-read)<a href="https://agentmods.dev/skills/d-mariano/spicyclaude/feasibility-cold-read"><img src="https://agentmods.dev/badge/skills/d-mariano/spicyclaude/feasibility-cold-read/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/d-mariano/spicyclaude/feasibility-cold-read"><img src="https://agentmods.dev/badge/skills/d-mariano/spicyclaude/feasibility-cold-read.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.00088 | $0.02568 |
| Opus 5 | $0.00044 | $0.01284 |
| Sonnet 5 | $0.00018 | $0.00514 |
| Haiku 4.5 | $0.00009 | $0.00257 |
Grade A, and why
feasibility-cold-read 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 11d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feasibility Cold-Read
You are performing a COLD-READ feasibility study on a technical design. You have not seen this design before and have no conversational context. Your only inputs are the files in the feature folder named below.
You cannot ask the user anything. If the artifacts are ambiguous, record the ambiguity in the Interpretations to Resolve section of the draft — do not file a finding that depends on guessing what the design "probably means."
Your job: extract claims, verify the load-bearing ones, synthesize findings with binding severity tiers, and write a findings draft. The parent workflow (or a human reading the draft directly) handles disposition.
Setup
- Resolve the feature folder. The argument is the task slug. Glob
/context/*-$ARGUMENTS/to find the folder. If no match or multiple matches, fail loudly in your final summary — do not guess. - Identify the TDD. Glob
/context/[nnn]-$ARGUMENTS/tdd-*.md. Use the highest-indexed version (or the one named in the prompt, if specified). Note the index[nnn]— your draft is written as.feasibility-[nnn]-draft.mdin the same folder. - Identify adjacent inputs. Look for
contracts-[nnn].md, a PRD (anyprd*.mdin the folder or parent), and research files. Record which were found. Missing inputs are not failures — they constrain what you can verify and you note that in the Scope section of the draft.
If a scope override appears in the prompt (dimensions, depth, specific concerns), respect it. Otherwise default to Standard depth covering all dimensions present in the TDD.
Read Everything in Full
Read every artifact in full. Do not skim. You have no conversational shortcut — re-reading is the only way to catch claims that the designer may have qualified elsewhere in the document.
Order: TDD first (the primary artifact), then contracts (field-level commitments that may invalidate design-level claims), then PRD (the constraints the design must satisfy), then prior research (what's already been validated — these claims are pre-verified and you should not re-research them).
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.
- 11d ago First seen · 151 lines · 88 tokens per session scan A f210b39a1a04
feasibility-cold-read is a skill published in the GitHub repository d-mariano/spicyclaude (5 stars, last pushed 1mo ago), licensed MIT. It adds 88 tokens to every session and 2,568 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-31.
Other skills, from other repositories
gemini-api-agent-platform
Guides the usage of the Gemini API on Agent Platform with the Google Gen AI SDK for enterprise AI applications. Covers SDK usage (Python, JS/TS, Go, Java, C#), capabilities like Live API, tools, multimedia generation, caching, and batch prediction.
open-source
Documentation reference for writing Python code using the browser-use open-source library. Use this skill whenever the user needs help with Agent, Browser, or Tools configuration, is writing code that imports from browseruse, asks about @sandbox deployment, supported LLM models, Actor API, custom tools, lifecycle…
gemini-api-dev
Use this skill when writing code that calls the Gemini API for text generation, multi-turn chat, multimodal understanding, image generation, video generation, streaming responses, background research tasks, function calling, structured output, or migrating from the old generateContent API. Covers SDK usage and best…
deepstream-sop
Use this skill when building, deploying, evaluating, debugging, or measuring latency for the DeepStream SOP Inference Microservice — a GPU-accelerated FastAPI service that detects whether operators perform assembly-line steps in order via event boundary detection (GEBD) plus VLM classification. Trigger even if the…
azure-search-documents-dotnet
Azure AI Search SDK for .NET (Azure.Search.Documents). Use for building search applications with full-text, vector, semantic, and hybrid search. Covers SearchClient (queries, document CRUD), SearchIndexClient (index management), and SearchIndexerClient (indexers, skillsets). Triggers: "Azure Search .NET"…
azure-search-documents-ts
Build search applications using Azure AI Search SDK for JavaScript (@azure/search-documents). Use when creating/managing indexes, implementing vector/hybrid search, semantic ranking, or building agentic retrieval with knowledge bases.