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 koolamusic/claudefiles --skill kickoffgit clone --depth 1 https://github.com/koolamusic/claudefilesWrote 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/koolamusic/claudefiles/kickoff)<a href="https://agentmods.dev/skills/koolamusic/claudefiles/kickoff"><img src="https://agentmods.dev/badge/skills/koolamusic/claudefiles/kickoff/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/koolamusic/claudefiles/kickoff"><img src="https://agentmods.dev/badge/skills/koolamusic/claudefiles/kickoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00054 | $0.01237 |
| Opus 5.5 | $0.00022 | $0.00495 |
| Sonnet 5.5 | $0.00011 | $0.00247 |
| Haiku 4.5 | $0.00005 | $0.00124 |
Grade A, and why
kickoff 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 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.
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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kickoff
One command to go from empty repo (or unfamiliar codebase) to a working project with full workflow infrastructure. Produces .project/PROJECT.md + ROADMAP.md, initializes jira and studio, and points you at the first sprint.
Input
$ARGUMENTS:
- Free text — a description of what this project is and what you're trying to build
- Empty — start with adaptive questioning to understand the project
Process
1. Understand the project
If the user provided a description, use it as the seed. Either way, explore:
- Codebase scan —
ls,package.json,Cargo.toml,go.mod,README.md,CLAUDE.md, recent git history. What exists already? - Stack detection — language, framework, database, deployment target
- Existing workflow state —
.jira/,.project/,.planning/(legacy),.workspacerc
Then ask focused questions via AskUserQuestion (max 4 questions, bundled):
- What is this project? (one sentence)
- Who uses it and what problem does it solve?
- What are the hard constraints? (stack, timeline, compliance, team size)
- What does "done" look like for the first milestone?
Skip questions the codebase already answers.
2. Set up infrastructure
Run these in sequence:
a. Studio — if no .workspacerc exists, invoke /studio:setup semantics (create workspace, symlinks, gitignore block, hook wiring). If .workspacerc already exists, skip.
b. Jira — if no .jira/ exists, invoke /jira:init semantics (bootstrap .jira/ with STATE.md, sprints/). If .jira/ already exists, skip.
c. Create .project/ — mkdir -p .project/. If studio is active, this will be a symlink into the workspace.
3. Write PROJECT.md
Write .project/PROJECT.md:
---
name: <project name>
created: <YYYY-MM-DD>
stack: <detected stack summary>
status: active
---
# <Project Name>
## Purpose
<2-3 sentences: what this project is and why it exists>
## Constraints
<bulleted list of hard constraints — technical, timeline, compliance, team>
## Success criteria
<what "done" looks like — measurable where possible>
## Stack
<language, framework, database, deployment, key dependencies>
## Team
<who's working on this — roles, not names if unknown>
## Decisions
<significant architectural or product decisions already made — reference CLAUDE.md, ADRs, or CONTEXT.md entries>
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 · 149 lines · 54 tokens per session scan A dde789115271
kickoff is a skill published in the GitHub repository koolamusic/claudefiles (121 stars, last pushed 11d ago), licensed MIT. It adds 54 tokens to every session and 1,237 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-30.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…