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 avizmarlon/agent-skills --skill new-projectgit clone --depth 1 https://github.com/avizmarlon/agent-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/avizmarlon/agent-skills/new-project)<a href="https://agentmods.dev/skills/avizmarlon/agent-skills/new-project"><img src="https://agentmods.dev/badge/skills/avizmarlon/agent-skills/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/avizmarlon/agent-skills/new-project"><img src="https://agentmods.dev/badge/skills/avizmarlon/agent-skills/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.00051 | $0.01732 |
| Opus 5.5 | $0.00020 | $0.00693 |
| Sonnet 5.5 | $0.00010 | $0.00346 |
| Haiku 4.5 | $0.00005 | $0.00173 |
Grade A, and why
new-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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
new-project — Full project bootstrap standard
This skill aggregates 25 core disciplines — engineering, product, testing, documentation, and security — into a single executable checklist. It exists because auto-triggering of individual skills is unreliable, and demanding that every new build apply the complete standard requires explicit invocation, not passive hopes.
Invoking new-project once = a guarantee that all mandatory skills below are consulted at the right moment in the project lifecycle.
How to run this (do this immediately on invocation)
- Create a TodoWrite checklist with one item per skill in the table below (25 items). This is the enforcement mechanism — it makes a skipped skill visible instead of silently lost.
- Work the phases in order. Within a phase, invoke each skill via the Skill tool using the
exact identifier in the
invokecolumn. Mark its todocompletedonce consulted. - "As-needed" skills (tagged ⟳) still get a todo. If genuinely not applicable this project
(e.g. no database, no external API), mark it
completedwith a one-line note "N/A — " rather than deleting it. The point is a conscious decision, never a silent skip. - Behavioral standards (tagged ✦) are rules, not Skill-tool calls — apply them as ongoing behavior for the whole session; tick the todo once you've internalized/announced them.
Do not batch all 25 Skill invocations into one turn — that floods context with end-of-session guidance while you're still planning. Pull each one in as its phase arrives.
The 25 — by lifecycle phase
Phase 0 — Orientation (always first, before any design)
| Skill | invoke | why here |
|---|---|---|
| Brainstorming | superpowers:brainstorming |
Explore intent/requirements/user intent BEFORE any build. Process skill — runs first. |
| Project context | (optional: load project OWNER.md / README if exists) | If project has existing vision/stack docs, read them. Else skip. |
| Search-first ✦ | (rule, not a skill) | Verify external facts (tool behavior, API limits, versioning, third-party state) before asserting them. Embedded behavior for the whole session. |
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 · 118 lines · 51 tokens per session scan A 49c6b464796a
new-project is a skill published in the GitHub repository avizmarlon/agent-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 51 tokens to every session and 1,732 once invoked, about $0.0002 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-31.
Other skills, from other repositories
docs-governance
Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references. Use when a user asks for documentation governance, project-knowledge organization, documentation integrity, or a deterministic docs audit…
meeting-action-items
Turn meeting notes into cited decisions, owners, tickets.
coordinator
Take over as coordinator of the current LangWatch drive: read the live state from disk (the lane roster, the newest handover, the shape counters), report it, then work the handover's next action by writing manifests and spawning lanes. Replaces pasting a brief out of a handover document - the state is read, never…
company-employee
The protocol every employee of a PenguinHarness organization follows — read the handbook first, act on [orgtrigger] work runs, schedule tickets from the desk session and do the work in ticket sessions, block instead of idling, ask the board in the all-hands channel before anything heavy, costly, irreversible or…
company-ceo
Run a PenguinHarness organization as its CEO — turn the mission into a ticket tree, hire HR and finance first, partition the shared workspace, schedule the calendar, open a channel per stream, review tickets and report to the board in the all-hands channel.
company-mirror
Run a PenguinHarness organization that mirrors a real company — one digital twin per real colleague, each twin's desk bound to that colleague's chat bot, twins answering what the handbook already knows and relaying the rest to one another instead of hiring, scheduling and filing tickets.