agentmods.dev

stack

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 CodeCodex

2 9d ago A scan 53 tokens original Apache-2.0
View the source file ericfitz/skills
Install

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.

agentmods
npx agentmods add skills/ericfitz/skills/stack
Any agent
npx skills add ericfitz/skills --skill stack
Clone the repo
git clone --depth 1 https://github.com/ericfitz/skills

Made for: Claude Code, Codex.

Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 640 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00053 $0.00640
Opus 5 $0.00026 $0.00320
Sonnet 5 $0.00011 $0.00128
Haiku 4.5 $0.00005 $0.00064

Measured yesterday against content hash 1b3cc8b5f45f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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 · 65 lines

How it starts

The opening of the file, as written. The whole thing — 65 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

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 — trust the census; go to step 4.
    • partial or low — the script found things it could not classify. Go to step 3.

  3. Fallback reading. Follow the order in references/ecosystems.md under "When the script comes back low-confidence". Read the repo yourself. Correct or extend the script's findings; never discard them silently.

  4. Determine runtimes and build_commands from the version files and build-command tables in references/ecosystems.md. Prefer a command actually present in a Makefile, justfile, or CI workflow over the ecosystem default.

  5. Determine monorepo: true when manifests appear in two or more distinct directories. List those directories in monorepo.packages.

  6. Emit the contract. Set inventory to the script's full JSON output verbatim. Set confidence to the script's coverage_confidence, downgraded one level if your fallback reading contradicted the script.

Read the full file on GitHub · 65 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. yesterday 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 (2 stars, last pushed 9d ago), licensed Apache-2.0. It adds 53 tokens to every session and 640 once invoked, about $0.0003 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.

TestingWriting and docs
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 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

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 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

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens