aod-stack

aod-stack is a skill for Claude Code from davidmatousek/agentic-oriented-development-kit. It costs 42 tokens per session (4,526 once invoked), scanned A, a copy of aod-stack, MIT.

A skill for managing technology-specific stack packs for coding agents. A stack pack is a set of project conventions, security patterns, and agent guidance for a particular technology setup.

In plain words
What is it for?
It lists available packs, activates or removes the active pack, and scaffolds a project structure from the selected pack.
Why use it?
It keeps an agent's instructions aligned with the selected technology and project structure. It also checks that a requested pack exists before activating it.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths.

Good fit It lists available packs, activates or removes the active pack, and scaffolds a project structure from the selected pack.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/davidmatousek/agentic-oriented-development-kit/aod-stack
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.

Any agent
npx skills add davidmatousek/agentic-oriented-development-kit --skill aod-stack
Clone the repo
git clone --depth 1 https://github.com/davidmatousek/agentic-oriented-development-kit

Made for: Claude Code.

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 aod-stack

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/davidmatousek/agentic-oriented-development-kit/aod-stack"><img src="https://agentmods.dev/badge/skills/davidmatousek/agentic-oriented-development-kit/aod-stack.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,526 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 100% copy Near-identical to another mod 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.00042 $0.04526
Opus 5.5 $0.00017 $0.01810
Sonnet 5.5 $0.00008 $0.00905
Haiku 4.5 $0.00004 $0.00453

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

Security

Grade A, and why

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

Origin

This is a copy

100% identical to aod-stack — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/aod-stack/SKILL.md · 501 lines

How it starts

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

Stack Pack Management Skill

Activate, list, and manage stack packs that encode technology-specific conventions, security patterns, and agent persona supplements into AOD.

Subcommands

Command Purpose
/aod.stack use {pack-name} Activate a stack pack
/aod.stack list Show available packs and active status
/aod.stack remove Deactivate the active pack
/aod.stack scaffold Scaffold project structure from the active pack

/aod.stack use {pack-name}

Activate a stack pack by copying its rules, generating a persona loader, and persisting activation state.

Step 1: Validate the pack exists

  1. Check that stacks/{pack-name}/ exists as a directory.
  2. Check that stacks/{pack-name}/STACK.md exists and is non-empty.
  3. If the directory or STACK.md does not exist, display the error:
    Pack not found: {pack-name}
    
    Available packs:
      - {list each directory under stacks/ that contains a STACK.md}
    
    Use: /aod.stack use {pack-name}
    
    Then stop.

Step 2: Handle already-active pack

  1. Read .aod/stack-active.json if it exists.
  2. If another pack is active (the pack field differs from {pack-name}):
    • Prompt the user: "Pack {current-pack} is currently active. Switch to {pack-name}? This will deactivate {current-pack} first. (y/n)"
    • If the user declines, stop.
    • If the user confirms, execute full deactivation: a. Delete all files in .claude/rules/stack/. b. Delete .aod/stack-active.json.
  3. If the same pack is already active (pack field equals {pack-name}):
    • Prompt: "Pack {pack-name} is already active. Re-activate to update rules and persona loader? (y/n)"
    • If the user declines, stop.
    • If the user confirms, proceed (this refreshes rules from the pack source).

Step 3: Detect and resolve inconsistent state

Before proceeding, check for inconsistencies:

  • If .aod/stack-active.json exists but is not valid JSON:
    • Warn: "Inconsistent state: .aod/stack-active.json is corrupted. Cleaning up stale state."
    • Delete all files in .claude/rules/stack/.
    • Delete .aod/stack-active.json.
    • Then continue with activation.

Read the full file on GitHub · 501 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. 1mo ago First seen · 501 lines · 42 tokens per session scan A bc455dab8d27

Subscribe to this mod's changes

aod-stack is a skill published in the GitHub repository davidmatousek/agentic-oriented-development-kit (24 stars, last pushed 3mo ago), licensed MIT. It adds 42 tokens to every session and 4,526 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to aod-stack, differing in 0 lines, and is treated as a copy.

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

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

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