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 policy-authorgit 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/policy-author)<a href="https://agentmods.dev/skills/runxhq/runx/policy-author"><img src="https://agentmods.dev/badge/skills/runxhq/runx/policy-author/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/policy-author"><img src="https://agentmods.dev/badge/skills/runxhq/runx/policy-author.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00066 | $0.00991 |
| Opus 5 | $0.00033 | $0.00495 |
| Sonnet 5 | $0.00013 | $0.00198 |
| Haiku 4.5 | $0.00007 | $0.00099 |
Grade A, and why
policy-author 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 7d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Policy Author
Produce one reviewable operational-policy proposal. Let the agent translate
intent into policy fields; let the native policy.lint tool decide whether the
exact in-memory result is a valid Runx policy.
Workflow
- Require concrete target repositories, source locators, owner routes, and an
available runner. Return
needs_inputwhen any are unresolved. - Draft the smallest
runx.operational_policy.v1that admits the stated work. Unspecified work remains denied. - When
existing_policyis supplied, preserve its target/source/runner set and only attenuate authority. Do not add locators, actions, targets, sources, or runners; do not lower confidence or weaken human gates. - Pass the draft to the deterministic validation step. Never author or trust an agent-supplied lint verdict.
- Return
readyonly when native lint passes. A native failure or attempted widening returnsrejectwith structured findings.
Native policy contract
Draft the exact contract consumed by policy.lint and the Runx policy parser:
schema: runx.operational_policy.v1
schema_version: runx.operational_policy.v1
policy_id: string
sources:
- source_id: string
provider: string
allowed_locators: [string]
allowed_actions: [string]
source_thread:
required: boolean
publish_mode: reply | comment | none
missing_behavior: fail_closed
minimum_confidence: number # optional
runners:
- runner_id: string
kind: string
state: available | unavailable
allowed_actions: [string]
target_repos: [owner/repo]
scafld_required: boolean
owner_routes:
- route_id: string
owners: [string]
target_repos: [owner/repo]
targets:
- repo: owner/repo
runner_ids: [string]
allowed_actions: [string]
default_owner_route: string
scafld_required: boolean
base_branch: string # optional
dedupe:
strategy: source_fingerprint
key_fields: [string]
on_duplicate: reuse | comment | block
outcomes:
observe_provider: boolean
verification_required: boolean
close_source_issue: never | when_verified | always
publish_final_source_thread_update: boolean
permissions:
auto_merge: boolean
mutate_target_repo: boolean
require_human_merge_gate: boolean
What ships with it
5 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.
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.
- 7d ago First seen · 123 lines · 66 tokens per session scan A 9c5da4bc2950
policy-author is a skill published in the GitHub repository runxhq/runx (84 stars, last pushed 2d ago), licensed Apache-2.0. It adds 66 tokens to every session and 991 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-09-03.
Other skills, from other repositories
dd-risk-scoring
Calculate weighted risk scores from specialist agent reports. Use when synthesizing multiple due diligence reports into an overall investment risk assessment.
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-sourcing
Document sources properly for due diligence reports. Use when citing any external data, ensuring full traceability and auditability of findings.
dd-verification
Verify claims in pitch decks and founder statements using multiple independent sources. Use when analyzing any claim about market size, traction, team background, or competitive positioning.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.