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 agentmods add instructions/garrytan/gstack/claude-mdgit clone --depth 1 https://github.com/garrytan/gstackWhat 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 | $0.11631 | $0.11631 |
| Opus 5 | $0.05816 | $0.05816 |
| Sonnet 5 | $0.02326 | $0.02326 |
| Haiku 4.5 | $0.01163 | $0.01163 |
Grade B, and why
gstack CLAUDE.md scanned grade B with 2 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 today.
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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
**Check once per session:** Run `ls -la .claude/skills/gstack` to see if it's a Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`test/egress-receipt-wiring.test.ts` fails CI on an unreceipted `curl` / How it starts
The opening of the file, as written. The whole thing — 801 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gstack development
Commands
bun install # install dependencies
bun run test # run free tests via the strict parallel runner (~90-100s full suite)
bun run test:evals # run paid evals: LLM judge + E2E (diff-based, ~$4.35/run max)
bun run test:evals:all # run ALL paid evals regardless of diff
bun run test:gate # run gate-tier tests only (CI default, blocks merge)
bun run test:periodic # run periodic-tier tests only (weekly cron / manual)
bun run test:gate:sharded # gate tier via the sharded paid runner (one Bun process per test file)
bun run test:periodic:sharded # periodic tier via the sharded paid runner (implies EVALS_ALL=1)
bun run test:e2e # run E2E tests only (diff-based, ~$4.20/run max)
bun run test:e2e:all # run ALL E2E tests regardless of diff
bun run eval:select # show which tests would run based on current diff
bun run dev <cmd> # run CLI in dev mode, e.g. bun run dev goto https://example.com
bun run build # gen docs + compile binaries
bun run gen:skill-docs # regenerate SKILL.md files from templates
bun run skill:check # health dashboard for all skills
bun run dev:skill # watch mode: auto-regen + validate on change
bun run eval:list # list all eval runs from ~/.gstack/projects/<slug>/evals/
bun run eval:compare # compare two eval runs (auto-picks most recent)
bun run eval:summary # aggregate stats across all eval runs
bun run eval:flake-rank # rank tests by flake signal (retried passes first; --json, --dir, --since-days)
bun run slop # full slop-scan report (all files)
bun run slop:diff # slop findings in files changed on this branch only
test:evals requires ANTHROPIC_API_KEY. Codex E2E tests (test/codex-e2e.test.ts,
test/codex-e2e-sol-scope.test.ts) use Codex's own auth — the hermetic runner copies
only auth.json from ${CODEX_HOME:-~/.codex} and pins CODEX_HOME in the child
env — no OPENAI_API_KEY env var needed.
Hermetic E2E + env keys: every E2E runner spawns children through
test/helpers/hermetic-env.ts (allowlist-scrubbed env, fresh seeded
CLAUDE_CONFIG_DIR, temp GSTACK_HOME, --strict-mcp-config); per-test
env: overrides merge last onto a COMPLETE hermetic env, so they're safe.
A PTY test that types a /skill command must pass seedSkills: true.
Debug against real operator state with EVALS_HERMETIC=0. Full detail
(env-shim, seeding tripwires, wiring tests):
docs/TESTING_INTERNALS.md.
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.
- today Changed · +1 lines · +39 tokens per session f3b6f9656ca5
- 2d ago First seen · 800 lines · 11,592 tokens per session scan B e2b0a141aeee
gstack CLAUDE.md is an instructions file published in the GitHub repository garrytan/gstack (130,961 stars, last pushed today), licensed MIT. It adds 11,631 tokens to every session, about $0.0582 per session on Opus 5. A static security scan graded it B with 2 findings (enumerates other installed skills, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.