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 skills/danshapiro/kilroy/starting-a-projectnpx skills add danshapiro/kilroy --skill starting-a-projectgit clone --depth 1 https://github.com/danshapiro/kilroyWrote 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/danshapiro/kilroy/starting-a-project)<a href="https://agentmods.dev/skills/danshapiro/kilroy/starting-a-project"><img src="https://agentmods.dev/badge/skills/danshapiro/kilroy/starting-a-project.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.00036 | $0.00470 |
| Opus 5 | $0.00018 | $0.00235 |
| Sonnet 5 | $0.00007 | $0.00094 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
starting-a-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 5d 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.
What it actually says
Starting A Project
Use this skill to prepare a clean repo for kilroy attractor validate/run. This skill does not create requirements artifacts; it only wires and verifies them.
Required Inputs
- Target repo path (clean directory)
- Existing project artifacts: spec (
*.md), DoD (*.md), graph (*.dot), run config (*.yamlor*.json) - Path to the Kilroy source repo (for canonical skill content and helper scripts)
Workflow
- Create the target directory and initialize git.
- Add canonical skill mounts:
skills -> <kilroy-repo>/skills.claude/skills/<name> -> ../../skills/<name>.agents/skills/<name> -> ../../.claude/skills/<name>
- Copy project artifacts into the new repo (commonly under
demo/): spec, DoD, graph, run config, and any graph-referenced companion files. - Update run config for the new repo:
- Set
repo.pathto the absolute target repo path. - Ensure absolute helper paths (for example
modeldbpath orscripts/start-cxdb.sh) still resolve on this machine.
- Create a base commit so Attractor can create run branches/worktrees.
- Verify readiness:
kilroy attractor validate --graph <graph.dot>- Confirm required executables and env vars expected by config/setup exist.
Guardrails
- Do not invent or regenerate spec/DoD/run config content in this skill.
- If any required artifact is missing or empty, stop and report the gap.
- Keep all setup deterministic and local-first (no production run side effects).
Done Checklist
- Target directory is a git repo with at least one commit.
- Skill symlink layout resolves (
skills,.claude/skills,.agents/skills). - Spec, DoD, graph, and run config are present and non-empty.
repo.pathin run config points at the new repo.- Graph validation returns no errors.
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.
- 5d ago First seen · 45 lines · 36 tokens per session scan A 038314df5009
starting-a-project is a skill published in the GitHub repository danshapiro/kilroy (219 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 470 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…