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 least-privilegegit 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/least-privilege)<a href="https://agentmods.dev/skills/runxhq/runx/least-privilege"><img src="https://agentmods.dev/badge/skills/runxhq/runx/least-privilege/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/least-privilege"><img src="https://agentmods.dev/badge/skills/runxhq/runx/least-privilege.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.00034 | $0.01974 |
| Opus 5 | $0.00017 | $0.00987 |
| Sonnet 5 | $0.00007 | $0.00395 |
| Haiku 4.5 | $0.00003 | $0.00197 |
Grade A, and why
least-privilege 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 8d 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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Least Privilege Auditor
Turn granted authority plus attributable observed usage into a bounded attenuation proposal.
This skill resolves every supporting receipt id through the native ledger
runner before comparing exercised scopes from Runx's redacted receipt detail
with the current grant. Native detail is authoritative for scope use. A supplied
usage summary exists only for deterministic replay of older evidence that lacks
that projection. Missing receipt proof defers every scope. The output is a
reviewable attenuation proposal, not an automatic change.
Composes
ledger#read
What this skill does
- Diff granted authority against receipt-backed usage.
- Classify each granted scope as
keep,narrow,remove, ordefer. - Propose the narrowest grant that still covers observed usage.
- State residual risk after attenuation.
- Emit a receipt-quality report a reviewer can apply or reject.
When to use this skill
- Periodic least-privilege review of a skill, grant, or principal before publish, renewal, or maturity promotion.
- After an incident, to identify authority that can be safely removed without breaking observed behavior.
- Before expanding distribution of a public skill, to prove its grant is minimal against real receipts.
- When a reviewer asks for a scope-by-scope evidence trail, not just a summary.
When not to use this skill
- To grant new authority. This skill only narrows; widening is a human decision.
- When no usable receipt evidence exists. Return
needs_more_evidencerather than guessing a grant down to nothing. - For secret material handling or credential exposure. Use the appropriate secret-leak triage flow instead of scope review.
- When the user asks for automatic permission changes. Produce a proposal and stop unless a separate approved delivery lane exists.
- When grant semantics are unknown and cannot be normalized. Return
needs_inputwith the exact syntax or policy question.
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.
- 8d ago First seen · 230 lines · 34 tokens per session scan A 537ba446b892
least-privilege is a skill published in the GitHub repository runxhq/runx (87 stars, last pushed 3d ago), licensed Apache-2.0. It adds 34 tokens to every session and 1,974 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-09-03.
Other skills, from other repositories
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.
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-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.