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/whchoi98/project-init/claude-mdgit clone --depth 1 https://github.com/whchoi98/project-initWrote 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.
[](https://agentmods.dev/instructions/whchoi98/project-init/claude-md)<a href="https://agentmods.dev/instructions/whchoi98/project-init/claude-md"><img src="https://agentmods.dev/badge/instructions/whchoi98/project-init/claude-md.svg" alt="Measured on agentmods" height="20"></a>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 | $0.01341 | $0.01341 |
| Opus 5 | $0.00671 | $0.00671 |
| Sonnet 5 | $0.00268 | $0.00268 |
| Haiku 4.5 | $0.00134 | $0.00134 |
Grade A, and why
project-init 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 4d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Context
Overview
project-init is a Claude Code plugin marketplace that provides project structure initialization, documentation quality scoring, and auto-sync workflows. The main plugin lives in plugins/project-init/.
Tech Stack
- Claude Code Plugin System (commands, skills, agents as Markdown/YAML)
- Bash (hook scripts, setup scripts)
- Git (version control, commit-msg hooks)
- Markdown (all plugin definitions, documentation, templates)
Project Structure
plugins/project-init/ - Main plugin source
.claude-plugin/ - Plugin manifest (plugin.json)
commands/ - Slash commands (init-project, sync-docs, generate-readme, etc.)
agents/ - Agent definitions (doc-sync-checker)
skills/project-scaffolder/ - Scaffolding skill with reference templates
.claude/ - Claude Code settings and project hooks
hooks/ - PostToolUse, PreToolUse, SessionStart, Notification hooks
skills/ - Project-level skills (code-review, refactor, release, sync-docs)
commands/ - Project-level slash commands (review, test-all, deploy)
agents/ - Project-level agents (code-reviewer, security-auditor)
docs/ - Architecture docs, ADRs, runbooks
decisions/ - Architecture Decision Records
runbooks/ - Operational runbooks
tests/ - Automated test suite (hooks, secret patterns, structure)
scripts/ - Setup and deployment scripts
.claude-plugin/ - Marketplace manifest (marketplace.json)
img/ - Images and assets
.github/ - GitHub issue/PR templates
Conventions
- Language: Bilingual (Korean/English) for all user-facing docs (README, CHANGELOG, architecture, ADR, runbook); see
writing-style-guide.md - Plugin structure: Commands are
.mdfiles with frontmatter; agents are.mdor.yml - Reference templates: Stored in
skills/project-scaffolder/references/as Markdown with embedded code blocks - Versioning: Semantic versioning; version tracked in
marketplace.jsonandplugin.json - Commit messages: Co-Authored-By lines auto-removed by commit-msg hook
- Indentation: 2 spaces (see
.editorconfig) - Line endings: LF
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.
- 4d ago First seen · 108 lines · 1,341 tokens per session scan A b076ae29c790
project-init CLAUDE.md is an instructions file published in the GitHub repository whchoi98/project-init (2 stars, last pushed 1mo ago), licensed MIT. It adds 1,341 tokens to every session, about $0.0067 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.