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.
/plugin marketplace add basher83/lunar-claudenpx agentmods add plugins/basher83/lunar-claude/blake-osgit clone --depth 1 https://github.com/basher83/lunar-claudeWrote 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/plugins/basher83/lunar-claude/blake-os)<a href="https://agentmods.dev/plugins/basher83/lunar-claude/blake-os"><img src="https://agentmods.dev/badge/plugins/basher83/lunar-claude/blake-os.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
blake-os 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 2d 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.
What it actually says
{
"name": "blake-os",
"version": "0.1.0",
"description": "Git workflow automation without the developer machinery",
"author": {
"name": "basher83",
"email": "[email protected]"
},
"repository": "https://github.com/basher83/lunar-claude",
"license": "MIT",
"keywords": [
"git",
"commits",
"workflow",
"automation",
"conventional-commits"
]
}
What it installs
The manifest is a name and a version. 4 skills travel with it, and installing the plugin installs all of them — 401 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 2d ago First seen · 19 lines scan A e7f90f48def5
blake-os is a plugin published in the GitHub repository basher83/lunar-claude (22 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
git-pr
Committing, PR creation and review triage, and dependency upgrades.
git
Git workflow tools: commits, PRs, review inbox, checkout, and work triage.
cas
Evidence-driven research, guarded Codex delegation, explicit native parallelism, secret protection, and approval gates for rm, commit, and push.
code-quality
OxLint, Biome, and Prettier configuration, linting skills, and pre-commit hooks for consistent code quality.
matt-pocock-skills
Bundled non-deprecated skills from Matt Pocock's Skills For Real Engineers (https://github.com/mattpocock/skills): engineering skills plus caveman, handoff, write-a-skill, git-guardrails-claude-code, and setup-pre-commit.
prek
Set up git pre-commit hooks with prek, the fast pre-commit-compatible runner.