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 skills add eugenelim/agent-ready-repo --skill init-projectgit clone --depth 1 https://github.com/eugenelim/agent-ready-repoWrote 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/skills/eugenelim/agent-ready-repo/init-project)<a href="https://agentmods.dev/skills/eugenelim/agent-ready-repo/init-project"><img src="https://agentmods.dev/badge/skills/eugenelim/agent-ready-repo/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/skills/eugenelim/agent-ready-repo/init-project"><img src="https://agentmods.dev/badge/skills/eugenelim/agent-ready-repo/init-project.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 156 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00126 | $0.02974 |
| Opus 5 | $0.00063 | $0.01487 |
| Sonnet 5 | $0.00025 | $0.00595 |
| Haiku 4.5 | $0.00013 | $0.00297 |
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 10d 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: init-project
The greenfield front door. An idea arrives and there is no repo yet — no foundation recorded, no first slice built. The temptation is to yolo a throwaway prototype, get it sort-of working, then retrofit structure and lose the rationale. This skill gives that path a home: it turns an idea into a structured repo by composing the skills the repo already owns. It orchestrates; it does not reinvent, and it is not an autonomous code generator — the human stays in the loop and the existing skills do the work.
It is the twin of adapt-to-project (the brownfield front door, for an
existing repo). Both converge on the same downstream loop:
brief → reference.md → spec → low-level design → work-loop.
When to invoke
Invoke when the unit of work is a brand-new repo from an idea and there are real stack / structure / tooling decisions ahead — a service, a library, a multi-component app someone will maintain. The tells: "start a new project", "bootstrap this idea into a repo", "we're greenfielding X".
Do not use it when:
- You are inside an existing codebase →
adapt-to-projectis the brownfield front door. - You want to author one feature from scratch →
new-spec. - The thing ahead is a script, a spike, or a throwaway with no real structural decisions → the trigger gate (stage 1) sends it straight to scaffolding; don't force the flow onto it.
The flow — five phases, fluid not waterfall
The five stages below are fluid phases of attention, not a waterfall. You revisit them as understanding firms up — authoring the walking skeleton routinely sends you back to amend the foundation, and that's the flow working, not failing. Each phase practises a scoped handoff: it passes the next phase only the artifacts that phase needs, nothing more.
The skill composes existing skills and assets by reference — it names them and hands off to them; it never restates their procedures and never imports their code.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 214 lines · 126 tokens per session scan A 155167ed16b8
init-project is a skill published in the GitHub repository eugenelim/agent-ready-repo (20 stars, last pushed today), licensed Apache-2.0. It adds 126 tokens to every session and 2,974 once invoked, about $0.0006 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-30.
Other skills, from other repositories
supervisor
Autonomous multi-agent quality supervisor and release gate. Use when a user wants the best possible result, asks for rigorous review, or when a substantive answer/deliverable should be challenged before release. Decomposes the task, fans out independent subagents, uses specialist and adversarial judges, verifies…
moai-platform-chrome-extension
Chrome Extension Manifest V3 development specialist covering service workers, content scripts, message passing, chrome. APIs, side panel, declarativeNetRequest, and Chrome Web Store publishing. Use when building browser extensions.
moai-framework-electron
Electron 33+ desktop app development specialist covering Main/Renderer process architecture, IPC communication, auto-update, and packaging with Electron Forge. Use when building cross-platform desktop applications.
moai-foundation-context
Manages context window optimization, session state persistence, and token budget allocation for multi-agent workflows. Use for token budget management, context limits, or session handoff across agents.
moai-platform-database-cloud
Cloud database platform specialist covering Neon (serverless PostgreSQL), Supabase (PostgreSQL 16 with real-time), and Firebase Firestore (NoSQL with offline sync). Use when choosing or setting up cloud databases.
review-claudemd
Review recent conversations to find improvements for CLAUDE.md files.