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 instructions/wilfredinni/noodle/agents-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/instructions/wilfredinni/noodle/agents-md)<a href="https://agentmods.dev/instructions/wilfredinni/noodle/agents-md"><img src="https://agentmods.dev/badge/instructions/wilfredinni/noodle/agents-md.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.08810 | $0.08810 |
| Opus 5 | $0.04405 | $0.04405 |
| Sonnet 5 | $0.01762 | $0.01762 |
| Haiku 4.5 | $0.00881 | $0.00881 |
Grade C, and why
noodle AGENTS.md scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
| **curl** | `curl -LsSf https://raw.githubusercontent.com/wilfredinni/noodle/main/scripts/install.sh \| sh` | Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Agent subcommand**: `agent install` writes the embedded `noodle-use` skill to `~/.agents/skills/noodle-use` and links detected Claude, Cursor, Codex, and OpenCode installations to that managed copy. It preserves unma How it starts
The opening of the file, as written. The whole thing — 447 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — noodle
Terminal REST client. Inspect, send, and iterate on HTTP requests from YAML files on disk. Built with OpenTUI (React binding) on Bun.
Quick commands
bun install
bun run dev -- --collection ./collections --env development
bun test # all tests (3117 across 204 files)
bun test tests/lang.test.ts # single file
bun run audit # fail on vulnerable dependencies
bun run lint # oxlint
bun run typecheck # tsc --noEmit
bunx oxfmt --check ./src ./tests # format check (oxfmt, only src+tests)
bun run build:bin # compile standalone binary via bun build --compile
bun run release:context # summarize public surfaces changed since the latest tag
bun run release:check -- --tag vX.Y.Z # validate code, docs site, and release readiness
CLI usage
noodle [<path>] [--collection <dir>] [--env <name>] [--noproxy] [--insecure]
noodle import <source> [--format <format>] [--output <dir>]
noodle export <collection> --format <openapi|postman> --output <file|dir>
noodle update
noodle agent install [--json] [--force]
noodle workspace list [--json]
noodle collection run <path> [<target>...] [--env <name>] [--tag <tag>]... [--exclude-tag <tag>]... [--fail-fast] [--delay <milliseconds>] [--noproxy] [--insecure] [--json]
noodle collection <create|init|list|inspect|format|audit> ... [--json]
noodle request <create|run> ... [--noproxy] [--insecure] [--json]
noodle cookie <list|clear> --collection <dir> [--json]
noodle environment set <key> <value> --env <name> [--collection <dir>] [--json]
noodle secret <set|list|delete> ... --env <name> [--collection <dir>] [--json]
- Default command (TUI mode): optional positional
<path>(use.for current directory),--collection/-c,--env/-e,--noproxy, and--insecure. Positional path overrides--collection; supplying both is invalid. Without either, the first existing registered collection in~/.config/noodle/config.ymlis used, then the current directory.--noproxyforces direct connections and--insecuredisables TLS verification for that invocation. - Import subcommand:
source(positional, required),--format/-i(openapi,swagger,postman, orinsomnia; auto-detected if omitted),--output/-o(default: ./collections) - Export subcommand:
collection(positional, required),--format(openapiorpostman), and--output/-o(a file for OpenAPI, or a new/empty directory for Postman). Postman createscollection.postman_collection.jsonplus one redacted environment file per environment; it preserves literal request values except that@/file paths expand to absolute home paths, so review exports for secrets and local path disclosure before sharing. - Update subcommand: Self-update. Reads
https://noodlerest.dev/update.json, caches verified release metadata for one hour (with a seven-day stale fallback), and SHA-256 verifies standalone binaries before replacement. Detects Homebrew installs and runsbrew upgrade noodle; unavailable in Bun development runtime. - Agent subcommand:
agent installwrites the embeddednoodle-useskill to~/.agents/skills/noodle-useand links detected Claude, Cursor, Codex, and OpenCode installations to that managed copy. It preserves unmanaged targets by default and reports every conflict;--forcedeliberately replaces all reported paths with backup-backed rollback if any target fails. Existing managed installations refresh after successful standalone, Homebrew, TUI, and curl-installer updates; refresh failures do not roll back Noodle and include a retry command. - Automation commands:
workspace list,workspace audit [--fix];collection create,init,list,inspect,format,audit [--fix],run [<target>...] [--env] [--tag]... [--exclude-tag]... [--fail-fast] [--delay <milliseconds>] [--noproxy] [--insecure];request create --url --method --collection,run [--env] [--noproxy] [--insecure];environment set;secret set|list|delete; andcookie list|clear --collection. They are non-interactive and support--json, which writes one{ status, data, errors }envelope and uses a nonzero exit status for invalid input, failed HTTP responses, failed captures, or failed assertions. Collection-run targets are request IDs or folder paths ending in/; folders include nested requests, overlapping targets run once in collection order, and omitting targets runs the whole collection. Request and non-root folder tags form case-sensitive dynamic suites; repeated include tags all must match, any repeated exclude tag removes a request, exclusion wins, and fail-fast records later selected requests as skipped.--delayaccepts a non-negative safe integer number of milliseconds and waits only between selected requests.cookie listprints jar contents grouped by domain (values included);cookie clearempties the jar.secret setprompts without echo in a TTY or accepts--stdin.collection formatcanonicalizes request YAML and pretty-prints valid JSON bodies without lossy numeric conversion; imports run it automatically.collection initbootstraps missing collection markers in an existing directory and registers it.workspace audit --fixremoves invalid registered paths. - Automation environment selection:
request runandcollection runuse--envwhen supplied; otherwise they use the collection root'ssettings.ymlenvironment. - Run-scoped variables: Every manual TUI send and
request rungets an isolatedRunScope; everycollection runshares one scope across its ordered requests. Resolved environment and secret values load first, then successful captures override the same names, with the latest successful capture winning. Failed captures leave prior values unchanged. Transient values disappear when the call returns. Manual sends andrequest runmay persist captures declared withpersist; collection runs and the TUI Runner ignore persistence. - TUI path modes: Existing collection roots open in collection mode. Directories containing request YAML but no collection markers open in read-only browse mode; empty directories open in read-only empty mode. Invalid or non-directory paths exit with an error. Initialize browse/empty directories from the command palette before editing or sending.
--help,--versionauto-generated by citty
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 · +1 lines · +35 tokens per session d2d50c69b2ec
- 2d ago Changed · +23 lines · +369 tokens per session 80ba0e316707
- 6d ago First seen · 423 lines · 8,406 tokens per session scan C 928e1600101f
noodle AGENTS.md is an instructions file published in the GitHub repository wilfredinni/noodle (301 stars, last pushed today), licensed Apache-2.0. It adds 8,810 tokens to every session, about $0.0440 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
symfony-flex-backend CLAUDE.md
Claude Code instructions for tarlepp/symfony-flex-backend, covering what is this?, table of contents ᐞ, ai documentation map ᐞ, version sources of truth ᐞ and project architecture ᐞ.
symfony-flex-backend copilot-instructions.md
Copilot instructions for tarlepp/symfony-flex-backend, covering what is this?, table of contents ᐞ, purpose ᐞ, architecture rules ᐞ and php and symfony rules ᐞ.
kavo CLAUDE.md
Claude Code instructions for kavo-labs/kavo, covering claude.md, what kavo is, commands, architecture and the request pipeline (the spine).
agent-of-empires AGENTS.md
AGENTS.md instructions for agent-of-empires/agent-of-empires, covering repository guidelines, where to look, commands, code rules and tests.
azure-sdk-for-go go-examples.instructions.md
Instructions for Azure/azure-sdk-for-go, a project described as: This repository is for active development of the Azure SDK for Go. For consumers of the SDK we recommend visiting our public developer docs at.
azure-sdk-for-go go-code.instructions.md
Instructions for Azure/azure-sdk-for-go: All code should follow the guidelines from the Azure Go SDK Guidelines. This document is a summary of the most important guidelines to follow when contributing to the Azure Go SDK.