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/loosewiredev/mealforge/feature-developmentnpx skills add LooseWireDev/mealforge --skill feature-developmentgit clone --depth 1 https://github.com/LooseWireDev/mealforgeWrote 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/loosewiredev/mealforge/feature-development)<a href="https://agentmods.dev/skills/loosewiredev/mealforge/feature-development"><img src="https://agentmods.dev/badge/skills/loosewiredev/mealforge/feature-development.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.00048 | $0.00676 |
| Opus 5 | $0.00024 | $0.00338 |
| Sonnet 5 | $0.00010 | $0.00135 |
| Haiku 4.5 | $0.00005 | $0.00068 |
Grade A, and why
feature-development 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 3d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Development
Every feature follows the same four-step flow. Do not skip steps or reorder them.
1. Spec first
A feature starts from a written spec (usually in docs/) covering behavior, edge cases, and acceptance criteria. If no spec exists, stop and ask for one — do not improvise requirements.
2. Scaffold with the generator
npx nx generate @<project>/project-plugin:feature --name <name> --apps <apps>
<project>is this project's package scope (check the rootpackage.jsonname ortools/project-plugin/package.json).--namemust be a camelCase identifier starting with a lowercase letter:userProfile, notuser-profileorUserProfile. It becomes${name}Routerand directory names; the generator rejects anything else.--appsis a comma-separated subset ofapi,web,mobile,desktop,static.
What the generator creates per app:
| App | Files |
|---|---|
| api | apps/api/src/features/<name>/ — router.ts, service.ts, service.test.ts, types.ts |
| web | apps/web/src/features/<name>/ — <Name>List.tsx, use<Name>Actions.ts, <Name>List.test.tsx |
| mobile | apps/mobile/src/features/<name>/ — same shape as web, React Native |
| desktop | apps/desktop/src-tauri/src/commands/<name>.rs |
| static | apps/static/src/pages/<name>/index.astro + island component |
Plus, always: a shared Zod schema stub at packages/shared/src/schemas/<name>.ts and an AGENTS.md stub in each feature directory.
Wiring (Hono backends): the generator automatically registers the feature router in apps/api/src/trpc.ts via the // forge:feature-imports and // forge:feature-routers anchor comments. Do not remove those anchors, and do not wire routers by hand.
Python backends: the generator scaffolds client-side features only. Create the apps/api feature module manually following apps/api/AGENTS.md and the fastapi-sqlalchemy-patterns skill.
3. Failing tests (separate session/agent from implementation)
Write tests from the spec into the generated *.test.ts(x) files — never from reading implementation. Run them; they must fail for the right reason (missing behavior, not syntax errors).
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.
- 3d ago First seen · 51 lines · 48 tokens per session scan A 6412e9f17b9c
feature-development is a skill published in the GitHub repository LooseWireDev/mealforge (1 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 676 once invoked, about $0.0002 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
fix-issues
Fix a batch of open GitHub issues end to end - one git worktree and one agent per issue (feature-dev for implementation, review-pr for review), individual PRs into develop, a release PR to main with a final multi-agent integration review, and optional tag/release/issue-comment publishing. Use when the user asks to…
add-mechanic
Add game mechanics with correct GDScript 4.x patterns -- movement, health, inventory, save/load.
debug-issue
Systematic Godot debugging decision trees for physics, signals, rendering, navigation, and input issues.
bulk-update
Update properties or content across many pages in a Notion database with dry-run and error recovery.
organize-database
Transform unstructured Notion pages into a well-designed database with proper schema and migration.
build-scene
Pattern-based Godot scene construction with node hierarchy templates and companion node rules.