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/uxname/litestack/new-projectnpx skills add uxname/LiteStack --skill new-projectgit clone --depth 1 https://github.com/uxname/LiteStackWrote 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/uxname/litestack/new-project)<a href="https://agentmods.dev/skills/uxname/litestack/new-project"><img src="https://agentmods.dev/badge/skills/uxname/litestack/new-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.00110 | $0.01483 |
| Opus 5 | $0.00055 | $0.00741 |
| Sonnet 5 | $0.00022 | $0.00297 |
| Haiku 4.5 | $0.00011 | $0.00148 |
Grade C, and why
new-project scanned grade C with 2 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 today.
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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .git && git init # drop template history; start the project's own Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST localhost:4000/graphql -H 'content-type: application/json' \ How it starts
The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The user wants to start a new project from LiteStack. The deliverable is a meta-repo with
backend/ and frontend/ submodules (the LiteStack shape) pointing at the team's own
repos (DERIVED mode), with the template identity renamed and the env contract satisfied.
This skill is the conductor. The mechanical steps are tested scripts at the meta root
(scripts/rename-project.sh, scripts/setup.sh, scripts/doctor.sh); the judgment steps
(creating remote repos, configuring Logto, confirming names) are yours to drive with the user.
Step 0: Gather inputs (ask the user)
- Project name (machine): lowercase
[a-z0-9-], e.g.acme-portal. Used for npm package names, the docker network, the theme store key. - Display brand (optional): human brand word, e.g.
Acme. Default = Title-Cased name. - Git host + owner: where the three repos will live (GitHub/GitLab org or user).
- Target directory for the new meta-repo checkout.
Confirm these before touching anything.
Step 1: Create the three remote repos
The new project needs its own meta, backend, and frontend repos on the team's host.
Create them as empty repos (no README), via gh/glab if available, otherwise ask the user to
create them and paste the URLs. You need three URLs:
<meta-repo-url>,<backend-repo-url>,<frontend-repo-url>.
Do not push anything yet.
Step 2: Scaffold the meta-repo
Clone the canonical LiteStack meta with submodules into the target directory, then detach from the upstream history so it becomes the team's own project:
git clone --recurse-submodules https://github.com/uxname/LiteStack <target-dir>
cd <target-dir>
rm -rf .git && git init # drop template history; start the project's own
Step 3: Repoint submodules + remotes to the team repos (DERIVED mode)
git config -f .gitmodules submodule.liteend-go.url <backend-repo-url>
git config -f .gitmodules submodule.litefront.url <frontend-repo-url>
git submodule sync
( cd backend && git remote set-url origin <backend-repo-url> )
( cd frontend && git remote set-url origin <frontend-repo-url> )
git remote add origin <meta-repo-url>
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.
- today Changed · -1 lines dbecb846cc2d
- 4d ago First seen · 128 lines · 110 tokens per session scan C 8da7a751a808
new-project is a skill published in the GitHub repository uxname/LiteStack (2 stars, last pushed yesterday), licensed MIT. It adds 110 tokens to every session and 1,483 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). 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.
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…