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 itechmeat/llm-code --skill project-creatorgit clone --depth 1 https://github.com/itechmeat/llm-codeWrote 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/itechmeat/llm-code/project-creator)<a href="https://agentmods.dev/skills/itechmeat/llm-code/project-creator"><img src="https://agentmods.dev/badge/skills/itechmeat/llm-code/project-creator/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/itechmeat/llm-code/project-creator"><img src="https://agentmods.dev/badge/skills/itechmeat/llm-code/project-creator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 103 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 105 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00065 | $0.01307 |
| Opus 5.5 | $0.00026 | $0.00523 |
| Sonnet 5.5 | $0.00013 | $0.00261 |
| Haiku 4.5 | $0.00006 | $0.00131 |
Grade A, and why
project-creator 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Creator
Guide creation and maintenance of project documentation in .project/ folder.
Quick Navigation
- Templates:
assets/folder - Guides:
references/folder
When to Use
- Starting a new project
- Creating/updating
.project/documentation - Planning user stories
Project Structure
.project/
├── about.md # Project overview, goals, target audience
├── specs.md # Technical specifications, versions
├── architecture.md # System architecture with diagrams
├── project-context.md # Cumulative decisions (optional)
└── stories/
├── stories.md # Master list
└── 001-story-name.md # Individual stories
Assets (Templates)
| Template | File | Purpose |
|---|---|---|
| About | assets/about-template.md |
Project overview |
| Specs | assets/specs-template.md |
Technical specs |
| Architecture | assets/architecture-template.md |
System architecture |
| Context | assets/project-context-template.md |
Project context |
| Stories List | assets/stories-template.md |
Stories master list |
| Story | assets/story-template.md |
Individual story |
Guides (References)
| Guide | File | Purpose |
|---|---|---|
| About | references/about-guide.md |
Questions & criteria |
| Specs | references/specs-guide.md |
Questions & criteria |
| Architecture | references/architecture-guide.md |
Questions & criteria |
| Context | references/context-guide.md |
Questions & criteria |
| Stories | references/stories-guide.md |
Questions & criteria |
Document Dependencies
about.md → specs.md → architecture.md → project-context.md → stories/
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/about-template.md 2.4 KB
- assets/architecture-template.md 7.2 KB
- assets/project-context-template.md 1.7 KB
- assets/specs-template.md 6.0 KB
- assets/stories-template.md 1.2 KB
- assets/story-template.md 862 B
- references/about-guide.md 2.4 KB
- references/architecture-guide.md 3.7 KB
- references/context-guide.md 3.2 KB
- references/specs-guide.md 3.0 KB
- references/stories-guide.md 3.6 KB
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 · 215 lines · 65 tokens per session scan A c80eecff455d
project-creator is a skill published in the GitHub repository itechmeat/llm-code (24 stars, last pushed 24d ago), licensed MIT. It adds 65 tokens to every session and 1,307 once invoked, about $0.0003 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
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.