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/41fred/ace-level1/claude-mdgit clone --depth 1 https://github.com/41fred/ace-level1What 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.01391 | $0.01391 |
| Opus 5 | $0.00696 | $0.00696 |
| Sonnet 5 | $0.00278 | $0.00278 |
| Haiku 4.5 | $0.00139 | $0.00139 |
Grade A, and why
ace-level1 CLAUDE.md 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Repository Purpose
This is your project repository with an AI workspace layer built in. Your files (code, documents, resources, whatever you're working on) live here, and Claude tracks progress, decisions, and goals automatically alongside them.
This is a starter — Ace Level 1. It ships with the minimum scaffolding to get a small team or solo operator working with Claude on day one. Larger systems (multi-project portfolios, custom hooks, MCP-driven analytics) layer on top of this once you outgrow the basics.
Workspace Structure
| Path | Purpose |
|---|---|
CLAUDE.md |
This file — workspace context Claude reads on every session |
README.md |
Public-facing intro and quick start |
tasks-inbox.md |
Open list of work not yet tied to an initiative |
goals/ |
YAML OKR system (created by goals-onboarding) |
goals-schema.md |
Reference spec for the OKR YAML format |
.claude/agents/ |
Installed AI agents |
.claude/hooks/ |
Python hooks (session-init, prompt-check) |
.claude/rules/ |
Always-active behavioral rules |
.claude/settings.json |
Permission mode and hook wiring |
.vscode/ |
Recommended VS Code extensions and workspace settings |
logs/temp/ |
Real-time work capture (consolidated into session logs) |
logs/archive/ |
Processed temp logs (excluded from search) |
level1.code-workspace |
VS Code workspace file — open this instead of code . |
Project Locations
| Project | Location | Description |
|---|---|---|
| (this workspace) | . |
Your work goes here. Add additional projects via start-here if you grow into a multi-repo setup. |
If you add additional repos later, start-here will register them here and create tracking folders.
Session Role
When working in this repo, Claude should:
- Help with project work (code, documents, planning, whatever the user needs)
- Track work automatically through temp logs and session logs
- Keep status and goals files updated as work progresses
- Surface active priorities and blockers when asked "what's the status"
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.
- 3d ago First seen · 120 lines · 1,391 tokens per session scan A 83f29a6fe4c3
ace-level1 CLAUDE.md is an instructions file published in the GitHub repository 41fred/ace-level1 (5 stars, last pushed 1mo ago), licensed MIT. It adds 1,391 tokens to every session, about $0.0070 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.
Other instructions, from other repositories
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).
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.
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.