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 aka-kika/akakika-skills --skill explain-new-projectgit clone --depth 1 https://github.com/aka-kika/akakika-skillsWrote 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/aka-kika/akakika-skills/explain-new-project)<a href="https://agentmods.dev/skills/aka-kika/akakika-skills/explain-new-project"><img src="https://agentmods.dev/badge/skills/aka-kika/akakika-skills/explain-new-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/aka-kika/akakika-skills/explain-new-project"><img src="https://agentmods.dev/badge/skills/aka-kika/akakika-skills/explain-new-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.00093 | $0.01445 |
| Opus 5.5 | $0.00037 | $0.00578 |
| Sonnet 5.5 | $0.00019 | $0.00289 |
| Haiku 4.5 | $0.00009 | $0.00145 |
Grade B, and why
explain-new-project scanned grade B with 1 finding 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 1mo 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
- Do not lecture about best practices unless it affects *their* next step How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explain New Project
Audience
The reader is self-taught (about two years of hands-on work), not tech-savvy, and learns best from everyday language. They are capable and curious—not beginners who need hand-holding, but people who want clarity without jargon walls.
Language rule
Write the report in the same language the user uses in chat (default: English). If they mix languages, follow their latest message.
"My own language" means:
- Short sentences, active voice
- No assumed CS degree
- Technical terms only when needed—and always explained (see Jargon rule)
- Analogies welcome when they clarify (one line max)
When invoked
- Confirm which folder is the project root (workspace root, or a path the user names).
- Explore before writing—do not guess. Read enough to be accurate.
- Write the full report using the template below.
- Always save
PROJECT_GUIDE.mdat the project root (same folder as README or main manifest). Overwrite if it already exists. - In chat: show the Quick start sections in full, then one line pointing to the file for the rest—e.g. Full guide saved to
PROJECT_GUIDE.md—scroll down there for the map, tech stack, gotchas, and next steps.
Exploration checklist
Work through these until you have a confident picture (skip what does not exist):
- [ ] README, README.*, docs/, AGENTS.md, CONTRIBUTING
- [ ] Top-level folders (what lives where)
- [ ] Manifest: package.json, pyproject.toml, Cargo.toml, go.mod, Podfile, etc.
- [ ] Entry points: main app file, index, App.tsx, src/main.*
- [ ] How to run: scripts in package.json, Makefile, docker-compose, .env.example
- [ ] Tests folder (if any)—only to say *whether* tests exist, not to teach testing
- [ ] .gitignore / deploy hints (Vercel, Docker, etc.)—plain words only
Use search/read tools; prefer evidence from files over assumptions.
Jargon rule
Whenever you use a term the reader might not know (API, dependency, build, deploy, framework, repo, branch, env var, etc.):
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.
- 1mo ago First seen · 148 lines · 93 tokens per session scan B f2979686e231
explain-new-project is a skill published in the GitHub repository aka-kika/akakika-skills (11 stars, last pushed yesterday), licensed MIT. It adds 93 tokens to every session and 1,445 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
apple-design
Cross-platform UI/UX design reviewer grounded in Apple's Human Interface Guidelines (123 pages pulled from developer.apple.com, including 57 component pages) plus a design-craft lens for distinctive, non-templated work. Use it to audit, review, critique, or improve any mobile app (iOS, Flutter, React Native) or…
oma-scholar
Search academic literature and generate, validate, or compare Knows paper sidecars. Use for claim/evidence analysis and literature synthesis.
pkf-writing
Author, update, convert, validate, persist, and render PKF (.pkf) content through message-inline, Library Asset, or Memory Page carriers. Use for structured reports, knowledge pages, delivery cards, or any .pkf body. NOT for recall, memory-graph placement, or curation decisions — those belong to the memory skill.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
work-with-creators-creator-vetting
Vets creators you have already named from their public pages. Covers the median views of their last 12 to 20 posts (sponsored and organic apart), a read of their comments, how often they post, audience fit with how sure it is, about 12 months of brand-safety checks, rival partnerships and rules for regulated…
loop-engineering
Shared loop-engineering reference for COG skills - the agent loop, deterministic verifiers, termination conditions, in-loop context management, and named patterns. Invoke when designing or debugging a skill that iterates (search-verify-retry, scan-until-dry, fetch-retry-gate).