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 devantler-tech/agent-plugins --skill needs-stack-mappinggit clone --depth 1 https://github.com/devantler-tech/agent-pluginsWrote 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/devantler-tech/agent-plugins/needs-stack-mapping)<a href="https://agentmods.dev/skills/devantler-tech/agent-plugins/needs-stack-mapping"><img src="https://agentmods.dev/badge/skills/devantler-tech/agent-plugins/needs-stack-mapping/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/devantler-tech/agent-plugins/needs-stack-mapping"><img src="https://agentmods.dev/badge/skills/devantler-tech/agent-plugins/needs-stack-mapping.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.00109 | $0.00952 |
| Opus 5.5 | $0.00044 | $0.00381 |
| Sonnet 5.5 | $0.00022 | $0.00190 |
| Haiku 4.5 | $0.00011 | $0.00095 |
Grade A, and why
needs-stack-mapping 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Needs → stack mapping
The person you are assisting describes what they want in the vocabulary of their product — an
outcome ("people should be able to book a session"), an audience ("my newsletter readers"), a
workflow ("when someone pays, send them the files"). Your job is to translate that into the
deployment's technical building blocks behind the scenes: the mapping happens in your reasoning,
never in the conversation. Conducted in the register of the jargon-free-voice skill.
Where the building blocks come from
The allowed building blocks are deployment-owned configuration, not part of this skill: the
consuming deployment's canonical instructions file (AGENTS.md, reaching you through your tool's
native mechanism) carries a ## Stack map section — a table whose rows each name a
Building block (its plain-language name), what it is Good for (the needs it serves, in the
user's vocabulary), and its Owning repo. That table is your entire menu:
- Match needs against the Good for column. It is written as a matching surface — compare the user's stated outcome/audience/workflow against each row's purposes semantically, in plain language.
- Never reach outside the map. Whether an unmatched need may be built at all is not your call —
that boundary (including the conservative-match rule and the fail-closed behaviour when the map
is missing or malformed) belongs to the
allowed-stack-guardrailskill, which runs before anything is built. This skill only ever selects from the map.
The procedure
- Elicit needs, not technologies. Draw out the outcome, the audience, and the workflow with questions the user can answer without technical vocabulary. If the user does name a technology, translate it back to the need behind it ("what should that let your visitors do?") rather than adopting it as a requirement.
- Map behind the scenes. Select the building block(s) whose Good for purposes cover the need. Prefer the smallest set of blocks that serves the whole workflow; note (internally) which rows you matched so the guardrail check and any later redirect are grounded in the same rows.
- Confirm behaviour, not design. Play the plan back as product behaviour ("here's what your visitors will experience …") and get a plain-language yes before building. The user approves described behaviour, never an architecture.
- Apply conventions silently. Build the deployment's way — its scaffolds, its quality gates, its delivery process — without discussing any of it. Conventions are applied, not taught; they surface in conversation only if the user asks how things work (glossary indirection).
- Report outcomes. Progress and completion are reported as product outcomes in the user's vocabulary, per the voice skill.
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 · 62 lines · 109 tokens per session scan A 4acc74fb1d36
needs-stack-mapping is a skill published in the GitHub repository devantler-tech/agent-plugins (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 109 tokens to every session and 952 once invoked, about $0.0004 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
top-design
Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions "Awwwards quality", "make my site stunning", "scroll animations", "parallax storytelling", "cinematic web design", "portfolio site", or "brand experience". Also trigger when elevating a standard…
design-everyday-things
Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", "mental model", "mapping", "seven stages of action", "users keep making…
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…
create-app
Guided journey from a raw app idea to a validated, cleanly architected first version that ships on a sustainable cadence. Orchestrates ten skills phase by phase - lean-startup, design-sprint, clean-architecture, domain-driven-design, clean-code, pragmatic-programmer, system-design, ios-hig-design, 37signals-way…
create-business
Guided journey from raw idea to a validated, positioned, priced business with a chosen beachhead. Orchestrates ten skills phase by phase - jobs-to-be-done, mom-test, design-sprint, lean-startup, good-strategy-bad-strategy, blue-ocean-strategy, obviously-awesome, hundred-million-offers, monetizing-innovation…
cold-start-problem
Start and scale networked products using Andrew Chen's "The Cold Start Problem" framework for network effects. Use when the user mentions "network effects", "chicken and egg", "cold start", "two-sided marketplace", "atomic network", "hard side", "liquidity", "critical mass", "invite-only launch", "how do I get my…