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.
git clone --depth 1 https://github.com/miounet11/ccjkWrote 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/commands/miounet11/ccjk/init-project)<a href="https://agentmods.dev/commands/miounet11/ccjk/init-project"><img src="https://agentmods.dev/badge/commands/miounet11/ccjk/init-project/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.
<a href="https://agentmods.dev/commands/miounet11/ccjk/init-project"><img src="https://agentmods.dev/badge/commands/miounet11/ccjk/init-project.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00017 | $0.00636 |
| Opus 5.5 | $0.00007 | $0.00254 |
| Sonnet 5.5 | $0.00003 | $0.00127 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade A, and why
init-project 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.
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Usage
/init-project <PROJECT_SUMMARY_OR_NAME>
Objective
Initialize project AI context using a mixed strategy of "concise at root + detailed at module level":
- Generate/update
CLAUDE.mdat repository root (high-level vision, architecture overview, module index, global standards). - Generate/update local
CLAUDE.mdin identified module directories (interfaces, dependencies, entry points, tests, key files, etc.). - ✨ For improved readability, automatically generate Mermaid structure diagrams in the root
CLAUDE.mdand add navigation breadcrumbs to each moduleCLAUDE.md.
Orchestration Instructions
Step 1: Call the get-current-datetime sub-agent to obtain the current timestamp.
Step 2: Call the init-architect sub-agent once, with input:
project_summary: $ARGUMENTScurrent_timestamp: (timestamp from step 1)
Execution Strategy (Agent adapts automatically, no user parameters needed)
- Stage A: Repository Census (Lightweight) Quickly count files and directories, identify module roots (package.json, pyproject.toml, go.mod, apps/, packages/, services/*, etc.).
- Stage B: Module Priority Scanning (Medium) For each module, perform targeted reading and sampling of "entry/interfaces/dependencies/tests/data models/quality tools".
- Stage C: Deep Supplementation (As Needed) If repository is small or module scale is small, expand reading scope; if large, perform batch supplemental scanning on high-risk/high-value paths.
- Coverage Measurement and Resumability
Output "scanned files / estimated total files, covered module ratio, ignored/skipped reasons" and list "recommended next-step deep-dive sub-paths". When running
/init-projectrepeatedly, perform incremental updates and breakpoint resumable scanning based on previous index.
Security and Boundaries
- Only read/write documentation and indexes, do not modify source code.
- Ignore common generated artifacts and binary large files by default.
- Print "summary" in main dialog, write full content to repository.
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 · 54 lines · 17 tokens per session scan A 2a8763e18038
init-project is a command published in the GitHub repository miounet11/ccjk (1 stars, last pushed 7d ago), licensed MIT. It adds 17 tokens to every session and 636 once invoked, about $0.0001 per session on Opus 5.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-30.
Other commands, from other repositories
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
research-verify
Verify existing research findings against independent primary sources. Upgrades confidence from 'sources agree' to 'independently verified.'.
discuss
A command that interviews you in five phases and saves a detailed description of a proposed feature or change. EARS is a structured way to write requirements so they can be checked clearly.
adr
A command that records important, difficult-to-reverse technical choices as Architecture Decision Records, or ADRs.
watch
You are executing the /hydra:watch command. Live monitoring of all background agents with real-time status updates.