A setup guide for adding SmartStack to a code repository and connecting it to AI coding tools. SmartStack keeps project context and working rules in shared repository files.

Use it to install SmartStack, add an adapter for Claude Code, Cursor, Codex, Windsurf, Copilot, or local Ollama, and fill in project details. It also covers repairing or extending the system.

It avoids setting up each AI tool from scratch and helps different tools follow the same project instructions. It also gives new sessions access to the project's background and past work.

setup — Skill for Claude Code and Codex by oreum-ai/smartstack

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 oreum-ai/smartstack --skill setup

Clone the repo

git clone --depth 1 https://github.com/oreum-ai/smartstack

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/oreum-ai/smartstack/setup/github.svg)](https://agentmods.dev/skills/oreum-ai/smartstack/setup)

Your own site

<a href="https://agentmods.dev/skills/oreum-ai/smartstack/setup"><img src="https://agentmods.dev/badge/skills/oreum-ai/smartstack/setup/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/oreum-ai/smartstack/setup"><img src="https://agentmods.dev/badge/skills/oreum-ai/smartstack/setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 628 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00628
Opus 5.5	$0.00000	$0.00251
Sonnet 5.5	$0.00000	$0.00126
Haiku 4.5	$0.00000	$0.00063

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

Security

Grade A, and why

setup 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 2mo 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.

ai-rules/skills/setup/SKILL.md · 38 lines

How it starts

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

Skill: Setup

When to use

Installing SmartStack into a repo for the first time, onboarding a new AI tool, or repairing/extending the system itself.

What this system is

A portable layer that lives in the repo so every AI session starts with full context, follows the same rules, recalls past work and bugs cheaply, and ships safely. Glued together by AGENTS.md + the ai-rules/ folder, with thin per-tool adapters in /adapters.

First-time install

Place the files at your repo root: AGENTS.md + the ai-rules/ folder.
Install your tool's adapter from /adapters:
- Claude Code → copy adapters/CLAUDE.md to repo root as CLAUDE.md.
- Cursor → copy adapters/.cursorrules to repo root (and optionally .cursor/rules/).
- Codex/OpenAI → AGENTS.md is already the file it reads; or copy adapters/AGENTS.codex.md notes.
- Windsurf/Antigravity → copy adapters/.windsurfrules to repo root.
- GitHub Copilot → copy adapters/copilot-instructions.md to .github/copilot-instructions.md.
- Ollama/local → paste adapters/ollama-system.md into the model's system prompt / Modelfile.
Fill in your project facts — edit ai-rules/context/project.md (10 min, one time; the template guides you). Optionally fill file-map.md, data-model.md, api-map.md, env-keys.md.
Make scripts runnable: chmod +x ai-rules/scripts/*.sh (Git Bash/WSL on Windows).
Confirm .gitignore excludes .env and secret files; run scripts/secret-scan.sh --all.
Verify your tool picks it up: open it in the repo and run the session-start hook.

Onboarding another AI tool

Point it at AGENTS.md first, then context/file-map.md and context/project.md. Tell it to follow ai-rules/rules/ and to use ai-rules/memory/ by index before inventing fixes. The summaries are tool-agnostic, so any capable assistant can resume from them.

Maintaining the system

Keep AGENTS.md short; push detail into context/.
Prune memory/sessions/ (the session-save/prune-sessions scripts do this).
Keep common-errors.md entries short and never delete them.
Update context/file-map.md and context/project.md when the codebase changes shape.
Run the doc-reviewer agent periodically to catch drift and bloat.

Read the full file on GitHub · 38 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.

2mo ago First seen · 38 lines · 0 tokens per session scan A ea91e13f650e

Subscribe to this mod's changes

setup is a skill published in the GitHub repository oreum-ai/smartstack (6 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 628 tokens. 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.

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