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 computerlovetech/agr --skill agr-cligit clone --depth 1 https://github.com/computerlovetech/agrWrote 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/computerlovetech/agr/agr-cli)<a href="https://agentmods.dev/skills/computerlovetech/agr/agr-cli"><img src="https://agentmods.dev/badge/skills/computerlovetech/agr/agr-cli/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/computerlovetech/agr/agr-cli"><img src="https://agentmods.dev/badge/skills/computerlovetech/agr/agr-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, 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 Rogue Agent · line 4 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Excessive Agency · line 56 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.
- medium Excessive Agency · line 237 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.
- medium Agent Snooping · line 62 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 128 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00147 | $0.03060 |
| Opus 5.5 | $0.00059 | $0.01224 |
| Sonnet 5.5 | $0.00029 | $0.00612 |
| Haiku 4.5 | $0.00015 | $0.00306 |
Grade A, and why
agr-cli 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 1mo 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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agr CLI
agr is the package manager for AI agent skills. It installs, shares, and syncs
SKILL.md folders across Claude Code, Cursor, Codex, OpenCode, GitHub Copilot,
and Pi. This skill helps you operate the agr CLI on the user's
behalf — set up new repos, install and sync skills, manage agr.toml /
agr.lock, and scaffold in-repo skills under skills/.
When to use
Use this skill when the user wants to:
- Install or remove a remote skill (
agr add anthropics/skills/pdf). - Sync
agr.tomlafter pulling teammates' changes (agr sync). - Upgrade an installed skill past its pinned commit (
agr upgrade). - Run a skill once without persisting it (
agrx ...) or invoke an installed one (agr run). - Scaffold a new skill (
agr init my-skill) — especially as in-repo skills underskills/. - Set up a repo from scratch to use agr (multi-tool config, instruction syncing, sources).
- Add a local in-repo skill to the project's dependency list.
- Inspect, edit, or troubleshoot
agr.toml/agr.lock/agr config. - Or whenever
agr.tomlis present and the user is doing resource-management work.
Do NOT use this skill for:
- Authoring the body of a SKILL.md. This skill scaffolds and registers; for
writing effective skill instructions, defer to the user or to a dedicated
authoring skill such as
anthropics/skills/skill-creator. - Iterating on an existing skill based on session feedback or a retrospective.
That's a separate workflow — listen, propose, edit, commit, re-install. If
the user has a dedicated debrief / improvement skill installed (e.g.
skill-debrief), use it; otherwise just do the workflow directly.
Prerequisites
Before running anything, verify agr is installed:
agr --version
If missing, the standard install is uv tool install agr. Do not install agr
without checking with the user first — they may prefer pipx, brew, or a
pinned version in CI.
Mental model — read first
- A skill is a folder containing a
SKILL.md. agr copies the whole folder into each configured AI tool's skills directory (.claude/skills/,.cursor/skills/,.opencode/skills/,.agents/skills/, etc.). - A handle identifies a remote skill:
user/skill(assumes a repo namedskills),user/repo/skill(any repo), or./local/path(on disk). agr.tomlis the manifest (hand-edited or written byagr add).agr.lockis the lockfile (auto-generated, pins commit SHAs and content hashes — never edit by hand).- Project-local vs global scope: every command takes
-gto operate on~/.agr/agr.tomland global tool dirs. agr synconly installs missing deps. To move past a pinned commit, useagr upgrade.- Resource types: skill (consumed by AI tools), ralph (autonomous
agent loop), package (a folder with its own
agr.toml, expanded transitively).agr addauto-detects the type.
What ships with it
8 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.
- 1mo ago First seen · 277 lines · 147 tokens per session scan A fcf1b053b4fa
agr-cli is a skill published in the GitHub repository computerlovetech/agr (452 stars, last pushed 2mo ago), licensed MIT. It adds 147 tokens to every session and 3,060 once invoked, about $0.0006 per session on Opus 5.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
linkedin-post
You take a YouTube video transcript and produce a single LinkedIn post draft.
ox-cli-attest
Publish a frozen Attest run to SageOx with ox attest publish --from --out . Read BEFORE publishing an Attest report, regenerating a report from a checkout, or debugging a failed or interrupted publish — ox publishes the frozen export only and never reconstructs a report from current files.
ox-cli-pr-header
Emit and paste the SageOx credit line at the TOP of a pull-request description — the human-facing counterpart to the machine SageOx-Session: trailer. Run ox pr header at PR-creation time; it renders a thin, on-brand, dark/light-aware single line linking the session(s), plan(s), and discussion(s) that produced the…
ox-cli-recap
Answer "what value am I getting from SageOx?" with receipts, not vibes. Auto-fire when the user asks "is SageOx worth it", "what has SageOx done for me", "what am I getting out of SageOx", "should I keep using this", "was SageOx worth it this week", or says "ox recap" / "give me a recap". Run ox recap --json and…
ox-cli-doctor
Run diagnostic checks on SageOx configuration and integrations.
ox-cli-init
Initialize SageOx for this repository.