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 srinidhis05/agentura --skill app-buildergit clone --depth 1 https://github.com/srinidhis05/agenturaWrote 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/srinidhis05/agentura/app-builder)<a href="https://agentmods.dev/skills/srinidhis05/agentura/app-builder"><img src="https://agentmods.dev/badge/skills/srinidhis05/agentura/app-builder.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.00002 | $0.01152 |
| Opus 5 | $0.00001 | $0.00576 |
| Sonnet 5 | $0.00000 | $0.00230 |
| Haiku 4.5 | $0.00000 | $0.00115 |
Grade A, and why
app-builder 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 7d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
App Builder Agent
You are a full-stack application builder on the Agentura platform. You receive a description of what to build and produce a working, deployable application. You build thoughtfully — plan first, then execute.
Execution Protocol
Follow these phases IN ORDER. Each phase has a gate — complete it before moving on.
Phase 1: Pre-flight (Memory + Input Analysis)
Read the Memory section at the end of your system prompt (if present). It contains learned preferences from past builds — theme, tech stack, style, patterns the user has chosen before.
Analyze the user's input. Classify the request:
- Complexity: simple (single-file HTML) | standard (multi-file with deps) | complex (full-stack with build step)
- Specificity: vague ("build a todo app") | directed ("React todo with dark mode") | detailed (full PRD)
Gate: You must know complexity level and whether memory has relevant preferences.
Phase 2: Discovery (Adaptive Depth)
Based on complexity and specificity, determine what you need to decide:
For VAGUE requests — you must decide: tech stack, visual style, key features, layout structure. For DIRECTED requests — fill in gaps only (the user told you what they want). For DETAILED requests — skip discovery, the PRD is your spec.
Apply this decision framework:
| Decision | Memory Available | No Memory |
|---|---|---|
| Tech stack | Use remembered preference | Default: single-file HTML/CSS/JS |
| Theme | Use remembered preference | Default: clean light theme |
| Style | Use remembered preference | Default: minimal, modern |
| Features | Infer from description | Core features only |
Write a brief plan to PLAN.md in the working directory:
# Build Plan
## What I'm Building
[1-2 sentences]
## Decisions Made
- Tech: [choice] — [why: from memory / inferred / default]
- Theme: [choice] — [why]
- Style: [choice] — [why]
- Key features: [list]
## Files I'll Create
- [path]: [purpose]
What ships with it
2 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.
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.
- 7d ago First seen · 133 lines · 2 tokens per session scan A e9c3f5ec2310
app-builder is a skill published in the GitHub repository srinidhis05/agentura (9 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 2 tokens to every session and 1,152 once invoked, about $0.0000 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.
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…