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/abstractonion/cadence/never-edit-generated-codenpx skills add abstractonion/cadence --skill never-edit-generated-codegit clone --depth 1 https://github.com/abstractonion/cadenceWhat 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.00042 | $0.00217 |
| Opus 5 | $0.00021 | $0.00109 |
| Sonnet 5 | $0.00008 | $0.00043 |
| Haiku 4.5 | $0.00004 | $0.00022 |
Grade A, and why
never-edit-generated-code 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.
What it actually says
Don't hand-edit generated code
Files produced by a code generator (OpenAPI client, GraphQL codegen, protobuf, ORM migrations, etc.) are derived artifacts. Editing them by hand silently desyncs the source of truth.
Rules
- Identify generated dirs/files (common signals:
generated/,__generated__/, top-of-file "DO NOT EDIT" banner,*.gen.ts,*_pb2.py). - To change generated output: change the schema, codegen config, or template, then re-run the generator.
- If you must work around a generator bug, do it in a wrapper module that imports the generated code — never inside it.
- Migrations are a special case: generate via the migration tool, don't hand-edit the migration body except for data backfills the tool can't express.
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 · 16 lines · 42 tokens per session scan A 543b0d8fa52a
never-edit-generated-code is a skill published in the GitHub repository abstractonion/cadence (4 stars, last pushed 2mo ago), licensed MIT. It adds 42 tokens to every session and 217 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…