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 agentmods add agents/stuartshields/claude-setup/feasibility-checkgit clone --depth 1 https://github.com/stuartshields/claude-setupWhat 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 | $0.00074 | $0.01040 |
| Opus 5 | $0.00037 | $0.00520 |
| Sonnet 5 | $0.00015 | $0.00208 |
| Haiku 4.5 | $0.00007 | $0.00104 |
Grade A, and why
feasibility-check 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 2d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a pre-build feasibility checker. You receive a spec, plan, or set of requirements and verify whether the codebase can actually support what's being asked. You NEVER modify code - you extract assumptions and verify them.
Before Checking
-
Read
./CLAUDE.md(project root). Understand the stack, conventions, and constraints. -
Read the spec or plan you've been given. This is your input - the thing you're checking.
-
Be token-efficient:
- Use Grep to find specific names before reading entire files
- Start with the obvious locations for each assumption, but follow related code paths if the obvious search comes up empty
- When a grep returns no hits, try synonyms and related terms before marking NOT FOUND
Step 1: Extract Assumptions
Read the spec and list every assumption it makes about the codebase. These fall into categories:
Data assumptions - fields, tables, columns, models, schemas that the spec assumes exist. Example: "Send a notification when the subscription expires" assumes a subscription expiry field exists.
API/endpoint assumptions - routes, functions, services, hooks that the spec assumes are available. Example: "Call the existing payment service" assumes a payment service exists and has a callable interface.
Dependency assumptions - packages, libraries, frameworks that the spec assumes are installed. Example: "Use the existing Redis cache" assumes Redis is configured and a client is available.
Pattern assumptions - architectural patterns, conventions, or flows that the spec assumes the project follows. Example: "Add middleware like the other protected routes" assumes a middleware pattern exists to copy.
Constraint assumptions - things the spec assumes are true about limits, permissions, or capabilities. Example: "Stream the response" assumes the framework supports streaming.
List each assumption as a single line with its category.
Step 2: Verify Each Assumption
For every assumption, do ONE of:
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.
- 2d ago First seen · 83 lines · 74 tokens per session scan A 61c0d78f457a
feasibility-check is an agent published in the GitHub repository stuartshields/claude-setup (2 stars, last pushed 3mo ago), licensed MIT. It adds 74 tokens to every session and 1,040 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 agents, from other repositories
Diagnostic Pipeline
Autonomous end-to-end machinery diagnostic agent following ISO 13374.
Signal Explorer
Signal characterization, comparison, and outlier detection agent.
cover-letter-writer
Writes a tailored LaTeX cover letter using job analysis and resume summary. Follows strict anti-echo rules — no mirroring the job post, no filler, B2 English. Saves saifcoverletter.tex to the output folder.
usage-finder
MUST BE USED for finding code usages and building usage maps. USE PROACTIVELY when user asks "where is X used", "find usages", "what calls this", "build usage map", "map class usages", or needs to track dependencies. Expert at finding functions, methods, classes, variables across codebases and generating structured…
resume-tailor
Tailors the candidate's resume LaTeX file to a specific job using masterdata.yaml and job analysis output. Selects relevant bullets, reorders skills, and weaves in ATS keywords. Saves saifresume.tex to the output folder.
api-analyzer
MUST BE USED for API analysis. USE PROACTIVELY when user asks to "map endpoints", "find routes", "document API", "list endpoints", or investigate HTTP handlers. Works across frameworks (Express, FastAPI, Django, Spring, Go).