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/hackbyrd/orbital-express/add-query-actionnpx skills add Hackbyrd/orbital-express --skill add-query-actiongit clone --depth 1 https://github.com/Hackbyrd/orbital-expressWrote 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/hackbyrd/orbital-express/add-query-action)<a href="https://agentmods.dev/skills/hackbyrd/orbital-express/add-query-action"><img src="https://agentmods.dev/badge/skills/hackbyrd/orbital-express/add-query-action.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.00064 | $0.00972 |
| Opus 5 | $0.00032 | $0.00486 |
| Sonnet 5 | $0.00013 | $0.00194 |
| Haiku 4.5 | $0.00006 | $0.00097 |
Grade A, and why
add-query-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 4d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add a Query (list) action
A Query action returns many records with pagination, sorting, and filtering. First define and get sign-off on authorization, filters, sort fields, pagination limits, response shape, and tests. Confirm complete structure with yarn repair <Feature> --dry-run, then yarn repair <Feature>. Use the add-action skill and yarn gen <Feature> -a V1Query to scaffold the action/test; never hand-create it. This skill covers the Query-specific body using helpers/cruqd.js.
The helpers (import from helpers/cruqd.js)
getOffset(page, limit)→ Sequelizeoffset.getOrdering(cols)→orderarray. Comma-separated; prefix-for DESC ('-createdAt,name').getOrderingWithModel(cols, models)→ ordering by associated-model columns ('user.lastName').convertStringListToWhereStmt(whereStmt, args, [{ name, col, isInt }])→ turns'1,2,3'arg into{ col: { [Op.in]: [...] } }and deletes the arg.parseUrlQueryFilter(args)→ converts bracket operators (createdAt[gte]) to Sequelize ops. Already run onreq.argsbymiddleware/args.jsfor every request — so range filters arrive pre-converted; just passreq.args(or a subset) intowhere.convertToSequelizeOps(obj)→ convert a Joi-validated{ gte, lte }object to Sequelize ops manually.numberComparisonSchema()(fromhelpers/schemas.js) → Joi for an exact number OR{ gte, lte, ... }.
Body pattern
async function V1QueryByUser(req, res) {
const schema = joi.object({
page: joi.number().integer().min(1).default(1),
limit: joi.number().integer().min(1).max(100).default(25),
sort: joi.string().default('-createdAt'),
status: joi.string().valid(...POST_STATUSES).optional(),
createdAt: numberComparisonSchema().optional(), // supports createdAt[gte] etc.
// ...other filterable fields
});
const { error, value } = schema.validate(req.args);
if (error) return errorResponse(req, ERROR_CODES.BAD_REQUEST_INVALID_ARGUMENTS, joiErrorsMessage(error));
req.args = value;
try {
// SECURITY: always scope the query to the owner — never return another user's rows
const whereStmt = { userId: req.user.id };
if (req.args.status) whereStmt.status = req.args.status;
if (req.args.createdAt) whereStmt.createdAt = convertToSequelizeOps(req.args.createdAt);
const { count, rows } = await models.post.findAndCountAll({
where: whereStmt,
order: getOrdering(req.args.sort),
limit: req.args.limit,
offset: getOffset(req.args.page, req.args.limit),
attributes: { exclude: models.post.getSensitiveData?.() || [] }
});
return { status: 200, success: true, posts: rows, total: count, page: req.args.page, limit: req.args.limit };
} catch (error) { throw error; }
}
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.
- 4d ago First seen · 60 lines · 64 tokens per session scan A 78f7bce1253c
add-query-action is a skill published in the GitHub repository Hackbyrd/orbital-express (14 stars, last pushed 15d ago), licensed MIT. It adds 64 tokens to every session and 972 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
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…