Borrowing it
Nothing to install: this file belongs to wilfredinni/noodle. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/wilfredinni/noodle/main/.agents/skills/noodle-dev/SKILL.mdgit clone --depth 1 https://github.com/wilfredinni/noodleWrote 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/wilfredinni/noodle/noodle-dev)<a href="https://agentmods.dev/skills/wilfredinni/noodle/noodle-dev"><img src="https://agentmods.dev/badge/skills/wilfredinni/noodle/noodle-dev.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.00052 | $0.03704 |
| Opus 5 | $0.00026 | $0.01852 |
| Sonnet 5 | $0.00010 | $0.00741 |
| Haiku 4.5 | $0.00005 | $0.00370 |
Grade A, and why
noodle-dev 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 today.
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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
noodle-dev
Terminal REST client. OpenTUI (React binding) on Bun. YAML files on disk.
REQUIRED BACKGROUND: Read AGENTS.md for CLI commands, stack, and conventions.
Quick routing
| Task | Read |
|---|---|
| Understand module boundaries, data flow, state, CLI, collection layout | architecture.md |
| Add a keybinding, pane, overlay, auth type, body type, hook, importer, CLI flag | recipes.md |
| Write tests for new feature | testing.md |
| Fix a bug or investigate a regression | testing.md → Bug-fix workflow |
| Add/modify persistent state (new files, config, timeline) | architecture.md → "Collection directory layout" |
| Build terminal UI components | REQUIRED SUB-SKILL: Use opentui skill |
Bug-fix workflow
For bug reports, keep investigation, regression-test creation, implementation, and review as separate stages. Never declare a bug fixed based only on code inspection.
- Reproduce the reported behavior before changing production code.
- When practical, add the smallest focused failing regression test that proves the defect.
- If the user requests investigation or approval first, stop after reporting the reproduction, likely root cause, and proposed minimal fix; do not implement until approved. Otherwise, continue with the authorized fix.
- Make the smallest localized change that passes the regression test. Do not refactor unrelated code or change behavior outside the reported bug.
- Never delete, skip, weaken, or broadly rewrite tests merely to make them pass.
- Run the focused test first, then the full test suite after the patch.
- Review the final diff for regressions and unintended behavior changes. Report the root cause, changed files, tests changed or added, commands run, user-visible behavior changes, and remaining risks.
What ships with it
3 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.
- today Changed 95b9f6a83e50
- yesterday Changed e7f091ea9631
- 2d ago Changed · +1 lines 86452cac1951
- 6d ago First seen · 105 lines · 52 tokens per session scan A eb3f31bb43cc
noodle-dev is a skill published in the GitHub repository wilfredinni/noodle (301 stars, last pushed today), licensed Apache-2.0. It adds 52 tokens to every session and 3,704 once invoked, about $0.0003 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
api-design-patterns
Comprehensive API design patterns covering REST, GraphQL, gRPC, versioning, authentication, and modern API best practices.
api-design
Use when settling the contract of an API you expose, before implementation: resources/URLs, REST vs GraphQL, versioning, one RFC 9457 error envelope, pagination, idempotency — emitted as OpenAPI 3.1. NOT implementing the endpoints (that is fastapi/nestjs/go/nodejs), NOT auth hardening (that is secure-coding), NOT…
geoserver-rest-api
Use when automating GeoServer management — programmatic workspace, datastore, and layer creation, style upload, service configuration via REST API. GeoServer REST API: manage GeoServer without GUI using curl, Python, or any HTTP client.
golang-http-frameworks
Go HTTP API development with net/http, Chi, Gin, Echo, and Fiber frameworks.
kavo-decorator
Reference for what @Kavo(Entity, config?) generates and how to configure/override it — routes table, EntityConfig shape (dto/allowed/operations), manual-method-wins, @Override, and fully custom routes. Use when writing or reviewing a @Kavo-decorated controller, or answering "how do I configure/override this route"…
policy
Reference for Kavo's policy authorization DSL — permission()/role()/owner()/authenticated()/filtered()/when() composed with and()/or()/not(), config placement, entity-aware nodes, enforcement order, and the authorization.required default-deny switch. Use when gating an operation on the caller (403 KAVOFORBIDDEN)…