add-action

A workflow for adding a new HTTP endpoint, which is a URL that an application can call, to an existing feature in an Express and Sequelize project.

In plain words
What is it for?
Use it to add actions such as canceling an order or updating a product, including the endpoint code, route integration, and integration test.
Why use it?
It avoids inconsistent route wiring, authorization, error handling, and tests when extending an API.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/hackbyrd/orbital-express/add-action
Any agent
npx skills add Hackbyrd/orbital-express --skill add-action
Clone the repo
git clone --depth 1 https://github.com/Hackbyrd/orbital-express

Made for: Claude Code, Codex.

Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,531 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00065 $0.01531
Opus 5 $0.00032 $0.00766
Sonnet 5 $0.00013 $0.00306
Haiku 4.5 $0.00006 $0.00153

Measured 3d ago against content hash c7e71b45a3f5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

add-action 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.

.claude/skills/add-action/SKILL.md · 43 lines

How it starts

The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Add an action to an existing feature

Actions are the real-time API handlers. Naming: V{version}{Action}[By{Role}][On{Device}] (e.g. V1Update, V1UpdateByAdmin). Read README "Actions Folder" + "Actions Folder Structure: Deep Dive".

Steps

  1. Plan/sign-off: define the endpoint contract, authorization, errors, side effects, route/controller wiring, and tests; get sign-off before scaffolding or edits. Confirm complete feature structure with yarn repair <Feature> --dry-run, then yarn repair <Feature>.

  2. Scaffold: yarn gen <Feature> -a V1<Action>. This validates names/targets first, exclusively creates the action + integration test, and deterministically rebuilds actions/index.js. Existing source/test conflicts abort before any write. Never hand-create or pass .js.

  3. Write the action (app/<Feature>/actions/V1<Action>.js) following the JS file structure:

    • JSDoc header: description, route(s) (GET/POST), the i18n note, auth requirement (Must be logged in/out/Can be both), Roles: [...], req.params, req.args (each arg typed: @id - (NUMBER - OPTIONAL) [DEFAULT - ...]), Success, and every Error: code (this list is your test checklist).
    • const i18n = lang.getLocalI18n();
    • Joi schema → validate req.args → on error return errorResponse(req, ERROR_CODES.BAD_REQUEST_INVALID_ARGUMENTS, joiErrorsMessage(error)); then req.args = value; (Joi has now coerced types: '5'5).
    • Business logic in a try. When returning a record, exclude sensitive fields: attributes: { exclude: models.<x>.getSensitiveData() }.
    • For multi-step writes, open a transaction (const t = await models.db.transaction()); on a business-rule failure mid-transaction use errorResponseRollback(t, req, ERROR_CODES.X); on success t.commit(). If you emit a socket event, emit after commit.
    • Flat success return: { status, success: true, ...payload } (201 on create, 202 on background-job handoff, else 200). Name keys after content; never nest under data.
    • In the catch, throw error (let it propagate to the error middleware — never return res.status(500)).
    • // END V1<Action>.

Read the full file on GitHub · 43 lines

Changes

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.

  1. 3d ago First seen · 43 lines · 65 tokens per session scan A c7e71b45a3f5

Subscribe to this mod's changes

add-action is a skill published in the GitHub repository Hackbyrd/orbital-express (14 stars, last pushed 14d ago), licensed MIT. It adds 65 tokens to every session and 1,531 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

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.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens