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/tomzx/agents/create-projectnpx skills add tomzx/agents --skill create-projectgit clone --depth 1 https://github.com/tomzx/agentsWhat 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.00073 | $0.01684 |
| Opus 5 | $0.00036 | $0.00842 |
| Sonnet 5 | $0.00015 | $0.00337 |
| Haiku 4.5 | $0.00007 | $0.00168 |
Grade A, and why
create-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 2d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Project
Populates the project context files under .sdlc/context/ by interviewing the user, so a new or empty project has full context before any feature work starts.
initialize-sdlc-directory creates the context files as stubs, and sync-sdlc fills them by analyzing existing code.
An empty project has no code to analyze, which leaves stubs.
This skill closes that gap: it asks, one topic per round, the questions the stubs need answered, and writes each file as its round completes.
goals.md is deliberately out of scope: /create-goals owns it (see Next Step).
Prerequisites
- Apply the shared SDLC conventions in
skills/sdlc/references/shared.md. - Optional project root (
$1); defaults to the current working directory. - The user is available to answer questions (this skill is interactive; never invent answers).
Steps
-
If the project root already contains source code (not just scaffolding like
.git/or a README), ask the user whether/sync-sdlcis the better tool, since code analysis produces more accurate context than an interview. Proceed only if the user confirms. -
If
.sdlc/does not exist at the project root, load and runinitialize-sdlc-directorywith$1first, per the Skill Handoff rule in shared.md, then continue here. -
Read every existing file under
.sdlc/context/. Sections that are already filled in count as answered; only ask about what is missing or still a placeholder. -
If
.sdlc/context/review-project.mdexists withverdict: changes-requested, operate in Revision Mode (below) instead of running the full interview. -
Run one interview round per topic, in this order. Each round presents four to six numbered questions about that topic only, then waits for the answers. The user may skip any question.
Round File Ask about 1 project-overview.mdWhat the project does and the problem it solves, key stakeholders, in-scope and out-of-scope capabilities, hard constraints (technical, business, regulatory) 2 architecture.mdMajor components and their responsibilities, how data flows between them, core domain entities and their relationships, intended topology. For an empty project, capture the intended architecture and mark it as planned 3 infrastructure.mdLanguage, runtime, framework, and database choices, development tooling and its exact commands, environments, CI/CD pipelines, deployment and rollback 4 conventions.mdNaming (files, functions, classes), directory structure, coding standards, commit message format, branching strategy, how SDLC artifacts should be written 5 vocabulary.mdDomain terms the project will use, technical terms, acronyms and abbreviations
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.
- 2d ago First seen · 135 lines · 73 tokens per session scan A c56d72b85524
create-project is a skill published in the GitHub repository tomzx/agents (5 stars, last pushed 5d ago), licensed MIT. It adds 73 tokens to every session and 1,684 once invoked, about $0.0004 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…