agentmods.dev

stack

stack is a skill for Claude Code from ericfitz/skills. It costs 53 tokens per session (901 once invoked), scanned A, original, Apache-2.0.

A codebase-profiling tool that identifies the languages, runtimes, package managers, build commands, and monorepo layout of a project. A monorepo is one repository containing multiple related projects or packages.

In plain words
What is it for?
Use it when onboarding to an unfamiliar repository or preparing for testing, dependency changes, or project documentation.
Why use it?
It gives later development tasks a reliable picture of how the repository is organised and built.

Skill for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the profile plugin — 4 skills shipped together

not rated 0repo changed 10d ago A scan 53 tokens original Apache-2.0

Good fit Use it when onboarding to an unfamiliar repository or preparing for testing, dependency changes, or project documentation.

Compare 6 skills from other repositories ↓
View source ↗ ericfitz/skills
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add ericfitz/skills
Claude Code
/plugin install profile

Made for: Claude Code.

Or install profile, the plugin that ships this one along with the rest of its 4 skills.

Wrote 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.

agentmods badge for stack

README.md
[![agentmods](https://agentmods.dev/badge/skills/ericfitz/skills/stack/github.svg)](https://agentmods.dev/skills/ericfitz/skills/stack)
Your own site
<a href="https://agentmods.dev/skills/ericfitz/skills/stack"><img src="https://agentmods.dev/badge/skills/ericfitz/skills/stack/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.

agentmods 80×15 button for stack

Your own site · 80×15
<a href="https://agentmods.dev/skills/ericfitz/skills/stack"><img src="https://agentmods.dev/badge/skills/ericfitz/skills/stack.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 901 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00053 $0.00901
Opus 5.5 $0.00021 $0.00360
Sonnet 5.5 $0.00011 $0.00180
Haiku 4.5 $0.00005 $0.00090

Measured 10d ago against content hash 0be8d8e1e6b4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

stack 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 10d 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.

profile/skills/stack/SKILL.md · 80 lines

How it starts

The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.

stack

Identify the ecosystem of a repository and emit the stack contract.

This is the gate phase for downstream discovery: every other phase's search strategy depends on knowing the ecosystem, and the inventory this phase produces is passed forward inside its contract so no downstream phase re-runs the script.

Bundled tool: ${CLAUDE_PLUGIN_ROOT}/scripts/profile_inventory.py Reference: ${CLAUDE_PLUGIN_ROOT}/references/ecosystems.md Contract: ${CLAUDE_PLUGIN_ROOT}/references/contracts/stack.schema.json Example: ${CLAUDE_PLUGIN_ROOT}/references/contracts/examples/stack.example.json

Usage

/profile:stack [path]     # default: current directory

path may be an extracted snapshot rather than a live checkout: an orchestrator running on a --ref snapshot passes the scan's scan_root (a git archive of the branch). To profile a branch standalone, check it out or extract it (git archive <ref> | tar -x -C <dir>) and pass that directory; this skill takes no --ref itself.

Output location

Emit the contract as your reply. When an orchestrating skill gives you a run dir, also save it to <run_dir>/stack.json. Standalone, keep it in the reply (or the session scratchpad if it is large) — never write it into the target repo.

Procedure

  1. Run the inventory script:

    uv run --script ${CLAUDE_PLUGIN_ROOT}/scripts/profile_inventory.py <path>

    --script is required: it isolates the run from the target repo's own project config, which would otherwise be resolved and can fail on repos with private indexes or unpublished dependencies.

    If uv is not installed, run the same path under python3 — this script declares no dependencies — and mention the fallback in your summary.

    Exit 2 means the path is unusable — stop and report that.

  2. Read coverage_confidence and unclassified.

    • high with an empty unclassified — trust the census; go to step 4.
    • high with a non-empty unclassified — read those files. Anything you cannot account for goes in unknowns[] and caps confidence at partial (step 6).
    • partial or low — the script found things it could not classify. Go to step 3.

Read the full file on GitHub · 80 lines

Changes

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.

  1. 10d ago Changed · +15 lines 0be8d8e1e6b4
  2. 1mo ago First seen · 65 lines · 53 tokens per session scan A 1b3cc8b5f45f

Subscribe to this mod's changes

stack is a skill published in the GitHub repository ericfitz/skills (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 53 tokens to every session and 901 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.

Planning
Related

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…

vercel/next.js · 123 tokens