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 opencue/cuecards --skill project-initializergit clone --depth 1 https://github.com/opencue/cuecardsWrote 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/opencue/cuecards/project-initializer)<a href="https://agentmods.dev/skills/opencue/cuecards/project-initializer"><img src="https://agentmods.dev/badge/skills/opencue/cuecards/project-initializer.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.1 | $0.00034 | $0.00620 |
| Opus 5 | $0.00017 | $0.00310 |
| Sonnet 5 | $0.00007 | $0.00124 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
project-initializer 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 3d 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.
This is a copy
100% identical to project-initializer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Initializer
Use exactly once per project, when session_mode == feature_loop and .agx/project/ does not yet exist (system prompt will say "Initializer 阶段").
Inputs
- A spec markdown, GitHub issue, or natural-language feature description.
- The repo root (
workspace_diror first non-default taskspace).
Steps
- Read the spec end-to-end. Use
file_readif the user pointed at a file, otherwise capture the user's message as the source of truth. - Decompose into ≥ 5 deliverables. Each feature must:
- have a stable
id(kebab-case, ≤ 32 chars), - be independently mergeable (its commit can land on main without breaking others),
- declare 1–3 concrete
acceptance_criteria(observable behavior, not implementation steps), - declare
depends_ononly for hard ordering constraints, - get an integer
priority(lower = sooner; reserve 100 for "later").
- have a stable
- Call
project_initwith the full feature list. The tool writesfeature_list.json, seedsstatus.jsonwithphase=initialize, and drops templateinit.sh+verify.yaml. - Customize
init.shviabash_exec(orfile_writewith the diff path =.agx/project/init.sh):- install language runtime / package manager dependencies,
- apply migrations / generate seed data,
- must be idempotent (running twice on the same machine should not break anything).
- Customize
verify.yamlwith the project's real test/lint commands. Keep thebootstrapstep that runsinit.sh. - Smoke-run with
verify_run(nofeature_id) to confirm the initial gate is green on a clean checkout. - Commit the harness files via
bash_exec:
Keep this commit small — only harness files, no business code.git add .agx/project init.sh verify.yaml git commit -m "chore(project): initialize harness with N features" - Append a closing progress note with
progress_append(e.g."[initialize-done] commit=<sha> features=N") and tell the user the project is ready for a Coding 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.
- 3d ago First seen · 51 lines · 34 tokens per session scan A ebe84b87e1d5
project-initializer is a skill published in the GitHub repository opencue/cuecards (5 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 620 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to project-initializer, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
{{BUCKET}}-management
Skill "{{BUCKET}}-management" from damusix/atomic-claude, covering purpose, doc shape and frontmatter contract.
loop
Full execution protocol for MODE: LOOP — the compound-engineering loop: brainstorm → plan → build → review → improve, iterating under defense-in-depth stop conditions with generator/critic separation, durable resumable state, and mandatory compounding learning capture. Loaded on demand by the architect when the loop…
memstack-business-client-onboarding
Use this skill when the user says 'client onboarding', 'new client', 'onboard client', 'kickoff meeting', 'intake form', 'welcome email', or needs welcome sequences, questionnaires, and setup checklists for new clients. Do NOT use for contracts or invoicing.
memstack-product-roadmap-builder
Use this skill when the user says 'roadmap', 'product roadmap', 'quarterly plan', 'now/next/later', 'OKRs', or needs strategic planning with themes, milestones, resource allocation, and stakeholder-ready views. Do NOT use for MVP scoping or sprint-level planning.
state
Use when the user says 'update state', 'project state', 'where was I', or at session start to load current context.
loongsuite-pilot-insight
A reporting workflow for turning LoongSuite Pilot and AI coding-agent logs into structured reports about events, teams, data quality, development efficiency, and AI use. It defines the meaning of the log fields and the measurements used in dashboards.