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 skills add runxhq/runx --skill business-opsgit clone --depth 1 https://github.com/runxhq/runxWrote 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/runxhq/runx/business-ops)<a href="https://agentmods.dev/skills/runxhq/runx/business-ops"><img src="https://agentmods.dev/badge/skills/runxhq/runx/business-ops/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/runxhq/runx/business-ops"><img src="https://agentmods.dev/badge/skills/runxhq/runx/business-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 144 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00040 | $0.02207 |
| Opus 5 | $0.00020 | $0.01104 |
| Sonnet 5 | $0.00008 | $0.00441 |
| Haiku 4.5 | $0.00004 | $0.00221 |
Grade A, and why
business-ops 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 9d 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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Business Ops
Turn one business signal into a replayable operations graph.
business-ops routes one signal into one selected bounded lane without giving
the agent ambient authority. The default route runner returns that typed
lane immediately; it does not require event-store configuration or run
unrelated docs, release, work, outreach, spend, and audit branches. Select
route_and_append only when a chain needs a durable event plus projection
readback, and select main only when the full planning fan-out is the
requested artifact.
This is not a provider integration and not an operator dashboard. It is the small core shape that teams copy when they want one objective to fan out into a chain of skills, then replay that chain with receipts.
The explicit route_and_append runner takes the same selected lane, appends
its packet through data-store, reads back the projection, and returns one
route_persistence result that distinguishes a new commit from an idempotent
replay while preserving the selected lane_packet. The same graph
can use local JSON, SQLite, Postgres, D1, Redis, or a product adapter by changing
the data_source_ref binding. Its aggregate id, expected version, and
idempotency key stay explicit because guessing them would corrupt durable
workflow state.
Composes
data-store#append_eventdata-store#read_projection
What this skill does
- Routes one business signal into one selected typed lane by default.
- Can explicitly fan the signal through representative lanes: docs, release, issue/PR, outreach planning, spend quoting, and proof audit.
- Produces structured lane packets with authority, gate, handoff, evidence, and readback fields.
- Demonstrates the runx split between proposal work and consequential action: drafts and plans can be produced, but sends, spend, merges, publishes, and deploys require a separate approval and execution lane.
- Gives downstream agents a clear handoff target instead of vague prose.
- Optionally persists the classified route for replay through
data-store.
What ships with it
11 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.
- business-ops.mjs 2.7 KB runs code
- fixtures/direct-default-route.yaml 1.6 KB
- fixtures/idempotent-route-replay.yaml 1.4 KB
- fixtures/launch-readiness-stops-before-effects.yaml 3.8 KB
- fixtures/missing-signal-stops-before-routing.yaml 775 B
- fixtures/route-and-append-sqlite.yaml 2.2 KB
- graph/ops-lane/ops-lane.mjs 9.7 KB runs code
- graph/ops-lane/SKILL.md 311 B
- graph/ops-lane/X.yaml 779 B
- harness/route-replay.yaml 1.2 KB
- X.yaml 6.9 KB
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.
- 9d ago First seen · 228 lines · 40 tokens per session scan A e5ed9fcb81e7
business-ops is a skill published in the GitHub repository runxhq/runx (84 stars, last pushed today), licensed Apache-2.0. It adds 40 tokens to every session and 2,207 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-30.
Other skills, from other repositories
gh-file-issue
Use when filing a new Codewhale GitHub issue: turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone.
gh-treasure-hunt
Hunt the issue/PR queue for highest value-over-risk wins: clean focused community PRs, already-implemented issues to close, safe quick-fixes.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
dd-synthesis
Synthesize findings from multiple specialist agents into a coherent investment recommendation. Use when combining reports from 9+ specialist agents into a single decision document.
dd-report-format
Standard output format for due diligence analysis reports. Use when producing your final analysis to ensure consistency across all specialist agents.
dd-risk-scoring
Calculate weighted risk scores from specialist agent reports. Use when synthesizing multiple due diligence reports into an overall investment risk assessment.