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/qaml-ai/camelai/developing-softwarenpx skills add qaml-ai/camelAI --skill developing-softwaregit clone --depth 1 https://github.com/qaml-ai/camelAIWhat 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.00085 | $0.01707 |
| Opus 5 | $0.00043 | $0.00853 |
| Sonnet 5 | $0.00017 | $0.00341 |
| Haiku 4.5 | $0.00009 | $0.00171 |
Grade A, and why
developing-software 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 2d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developing Software
Read this file completely once per task before the first create_project call. Do not reread it during the same task unless the instructions change. Read a reference below with read_skill({ skill: "developing-software", file: "<filename>" }); do not use the generic project/workspace file tools for skill files.
Workflow
- Choose the template for the dominant user experience.
- Create the project with a concise description and an explicit
template. - Inspect the seeded files before editing. Treat the scaffold as working architecture, not disposable sample code.
- Reshape the starter into the requested product. Rename the example entity, schema, routes, actions, validation, and UI copy consistently instead of adding a second implementation beside the demo.
- In React Router projects, add standard UI through
add_shadcn_component; do not hand-write components or page shells that the bundled registry provides. Invanillaprojects, work directly inpublic/. - Use
deploy_projectdirectly to build, publish, return the live URL, and open the app in preview. No manualset_previeworlist_appscall is needed afterward;set_previewremains available when you explicitly want to reopen or switch previews. Passdry_run: trueonly when the user explicitly wants validation without publishing. - Treat a successful deploy as sufficient completion evidence for routine build-and-ship requests. Do not automatically launch
env.BROWSERor capture screenshots after every deploy. Use browser or visual verification only when the user asks for it, the task is specifically diagnosing a deployed UI/runtime issue, or the task explicitly requires browser evidence.
Use camelAI project tools for scaffolding, dependencies, builds, and deploys. Do not run create-worker, wrangler init, npm create cloudflare, package-manager deploy commands, or shell-based scaffolding.
Template Selection
| Template | Choose when |
|---|---|
crud |
The product is primarily a stateful app, admin tool, tracker, portal, or workflow. This is the default and includes React Router loaders/actions plus Durable Object SQLite CRUD. |
vanilla |
The experience is client-only plain HTML/CSS/JavaScript: a small site, landing page, calculator, quiz, interactive demo, or simple DOM/canvas game. Prefer crud when it needs accounts, durable server records, a shared leaderboard, or multiplayer state. |
ai-chat |
Conversation or direct model interaction is the primary experience. An otherwise stateful app with one AI-assisted feature should normally remain crud and add the AI binding. |
integration-dashboard |
Discovering, monitoring, or operating workspace-connected SaaS/database services is central. If connections only provide business metrics, prefer data-dashboard. |
data-dashboard |
Users interact with KPIs, filters, charts, tables, exports, or drill-downs. |
data-analysis |
The deliverable is a notebook-first, read-only analytical report. Use the data-analysis skill and run_notebook; do not treat it like a React app. |
What ships with it
5 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.
- 2d ago First seen · 93 lines · 85 tokens per session scan A 0f03a7ab13d9
developing-software is a skill published in the GitHub repository qaml-ai/camelAI (357 stars, last pushed 3d ago), licensed MIT. It adds 85 tokens to every session and 1,707 once invoked, about $0.0004 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-30.
Other skills, from other repositories
huggingface-spaces
Build, deploy, and maintain applications on Hugging Face Spaces — Gradio / Docker / Static SDKs, ZeroGPU and dedicated hardware, model loading, debugging, buckets, inference providers, community grants. Use whenever the user asks to create or host an app on Hugging Face, port code onto ZeroGPU, fix a Space that won't…
kagent-dev
Development guide for kagent's v1alpha3 Harness and AgentTemplate CRDs, AgentInstance gRPC control plane, upstream A2A integration, Substrate runtime provisioning, tests, generation, and PR workflow. Use for any implementation, debugging, review, or CI task in the kagent repository.
timoni
Use when deploying applications to Kubernetes with Timoni. Covers installing and upgrading module instances from OCI registries, composing multi-app deployments with bundles, injecting values from clusters or CI with runtimes, targeting multiple clusters, and authoring, testing, signing and publishing modules with CUE.
azmon-mirroredcatalogs-operations-cli
Brings Azure Monitor, Application Insights, and Log Analytics telemetry into Fabric as Eventhouse external delta tables and correlates it with business data. Use to onboard observability data, judge whether latency or availability affected revenue, or build a Real-Time dashboard and Operations Agent over it.
durable-objects
Create and review Cloudflare Durable Objects. Use when building stateful coordination (chat rooms, multiplayer games, booking systems), implementing RPC methods, SQLite storage, alarms, WebSockets, or reviewing DO code for best practices. Covers Workers integration, wrangler config, and testing with Vitest. Biases…
ship-web-games
Package, deploy, and verify a playable Three.js or web game. Use for release builds, asset delivery, private/public deployment, production smoke tests, browser proof, release notes, rollback readiness, and cleanup of temporary QA resources.