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 alonf/specrew --skill upstream-blocker-documentationgit clone --depth 1 https://github.com/alonf/specrewWrote 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/alonf/specrew/upstream-blocker-documentation)<a href="https://agentmods.dev/skills/alonf/specrew/upstream-blocker-documentation"><img src="https://agentmods.dev/badge/skills/alonf/specrew/upstream-blocker-documentation/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/alonf/specrew/upstream-blocker-documentation"><img src="https://agentmods.dev/badge/skills/alonf/specrew/upstream-blocker-documentation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00024 | $0.01042 |
| Opus 5.5 | $0.00010 | $0.00417 |
| Sonnet 5.5 | $0.00005 | $0.00208 |
| Haiku 4.5 | $0.00002 | $0.00104 |
Grade A, and why
upstream-blocker-documentation 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.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
When an external dependency (upstream library, CLI, or service) has a known issue that blocks user workflows, user-facing documentation must guide users through:
- Awareness: What the blocker is and when they'll hit it
- Verification: How to confirm they've hit the specific issue (not a different error)
- Recovery: Immediate workarounds (downgrade, retry in different environment) and future path (monitor upstream issue)
Without this structure, users fail mid-workflow with cryptic errors and no recovery guidance.
Patterns
1. Tier-1 Blocker Placement in Prerequisites
Place known blockers upfront in the Prerequisites section, not buried in Known Limitations. Users need to know before they start, not fail mid-bootstrap.
Example from docs/getting-started.md:
- **Spec Kit CLI** (installed via `uv`): Must be operational in your environment.
⚠️ **Known blocker**: Spec Kit CLI may fail with `No matching release asset found for copilot`
due to a copilot asset dependency issue. If this occurs, see Known Limitations below.
2. Verification Step (confirm vs. different error)
Provide a specific command that reproduces the blocker. Users can confirm they hit this issue, not a different failure mode.
Example:
# User runs this to check if they hit the asset blocker:
specify init --here --ai copilot --script ps --ignore-agent-tools --force
If they see No matching release asset found for copilot, it's this blocker. If they see something else, they have a different issue.
3. Immediate Workaround (pinned version or alternate environment)
Provide a workaround users can apply now, not "wait for upstream fix":
Example:
# Downgrade to known-working version:
uv tool install --upgrade "specify-cli==0.7.3"
pwsh -File C:\Dev\Specrew\scripts\specrew-init.ps1 -ProjectPath . -Force
Or: "Try running in Windows Terminal instead of PowerShell 5.x" (environment change)
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 · 109 lines · 24 tokens per session scan A 97530177e003
upstream-blocker-documentation is a skill published in the GitHub repository alonf/specrew (55 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 1,042 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…