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 bugrabilge/bilge-development-kit --skill app-buildergit clone --depth 1 https://github.com/bugrabilge/bilge-development-kitWrote 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/bugrabilge/bilge-development-kit/app-builder)<a href="https://agentmods.dev/skills/bugrabilge/bilge-development-kit/app-builder"><img src="https://agentmods.dev/badge/skills/bugrabilge/bilge-development-kit/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.00028 | $0.01836 |
| Opus 5 | $0.00014 | $0.00918 |
| Sonnet 5 | $0.00006 | $0.00367 |
| Haiku 4.5 | $0.00003 | $0.00184 |
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 4d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
App Builder
"Weeks of coding can save you hours of planning." -- Unknown
When to Use
- Scaffolding a new full-stack application from scratch
- Setting up monorepo structures with multiple packages or services
- Configuring CI/CD pipelines for automated testing and deployment
- Choosing and configuring project templates and starter kits
- Establishing project conventions (linting, formatting, commit hooks)
- Planning technology stack decisions for new projects
Project Scaffolding Principles
Before Writing Code
- Define the scope: What does the MVP look like? What are the core features?
- Choose the stack: Pick technologies based on team expertise, requirements, and ecosystem maturity
- Design the data model: Sketch entities, relationships, and access patterns before coding
- Plan the API surface: Define endpoints or queries/mutations before implementing
- Set up the repository: Structure, tooling, and CI/CD before feature development
Directory Structure Conventions
A well-organized project follows predictable patterns:
project-root/
apps/ # Application entry points
web/ # Frontend application
api/ # Backend API server
mobile/ # Mobile application
packages/ # Shared libraries
ui/ # Shared UI components
config/ # Shared configurations
types/ # Shared TypeScript types
utils/ # Shared utility functions
infra/ # Infrastructure as code
scripts/ # Build and maintenance scripts
docs/ # Project documentation
Technology Stack Selection
Frontend Frameworks
| Framework | Best For | Considerations |
|---|---|---|
| Next.js | Full-stack React, SSR/SSG, SEO | Vercel ecosystem, app router maturity |
| Nuxt | Full-stack Vue, SSR/SSG | Vue ecosystem, auto-imports |
| SvelteKit | Performance-critical apps | Smaller ecosystem, growing fast |
| Remix | Nested routing, progressive enhancement | React Router foundation |
| Astro | Content-heavy sites, multi-framework | Content collections, island architecture |
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.
- 4d ago First seen · 197 lines · 28 tokens per session scan A 415f3b2f7fd1
app-builder is a skill published in the GitHub repository bugrabilge/bilge-development-kit (10 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 1,836 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
add-azuredevops
Adds Azure DevOps connector to a Power Apps code app. Use when querying work items, creating bugs, managing pipelines, or making ADO API calls.
atmos-modernization
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…