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 uxname/LiteStack --skill full-stack-featuregit 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/full-stack-feature)<a href="https://agentmods.dev/skills/uxname/litestack/full-stack-feature"><img src="https://agentmods.dev/badge/skills/uxname/litestack/full-stack-feature/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/uxname/litestack/full-stack-feature"><img src="https://agentmods.dev/badge/skills/uxname/litestack/full-stack-feature.svg" alt="Reviewed on agentmods" width="80" 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.00047 | $0.00331 |
| Opus 5.5 | $0.00019 | $0.00132 |
| Sonnet 5.5 | $0.00009 | $0.00066 |
| Haiku 4.5 | $0.00005 | $0.00033 |
Grade A, and why
full-stack-feature 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 11d 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.
What it actually says
The user wants a feature touching both sides. This skill only decides the order; the
work itself follows each sub-project's own AGENTS.md and the .agents/*.md it routes to.
Why backend first, and the full ordering rule: .agents/CROSS-PROJECT.md
→ "The four seams", seam 1.
The order
- Backend.
cd backend, readbackend/AGENTS.md, do the work,task checkgreen. Schema change → editinternal/graph/schema.graphqls→task gen→ resolver. - Bring it up so the schema is live:
task start:dev(Docker db+redis+object store, migrations at startup, GraphQL onlocalhost:4000/graphql). - Sync the contract only if the schema changed:
cd ../frontend && npm run gen. A failure here almost always means the backend is not up. - Frontend. Read
frontend/AGENTS.md, follow its routing table, build the UI from@generated/*,npm run checkgreen. - Commit with the meta
/commitskill — submodules first, then the pointers.
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.
- 11d ago Changed · -5 lines · -51 tokens per session 7c30618ecfe0
- 1mo ago Changed · -64 lines d90e4608c08a
- 1mo ago Changed 938a351014c4
- 1mo ago First seen · 93 lines · 98 tokens per session scan A aeb260680ba4
full-stack-feature is a skill published in the GitHub repository uxname/LiteStack (2 stars, last pushed 4d ago), licensed MIT. It adds 47 tokens to every session and 331 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-31.
Other skills, from other repositories
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
dev-runtime
How the Node side of a dev stack runs without haven, and the backend host: pnpm dev (UI built once, backend reloading), pnpm dev:hmr (adds the Vite ui lane), tools/dev-runtime (api + worker in one Node process), backend reload on a file change, the debounce (quiet window + max wait), ports derived from PORT. Use when…
migrate-segw-to-rap
Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…