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 baek-labs/hamesnpx agentmods add plugins/baek-labs/hames/claudegit clone --depth 1 https://github.com/baek-labs/hamesWrote 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/baek-labs/hames/claude)<a href="https://agentmods.dev/plugins/baek-labs/hames/claude"><img src="https://agentmods.dev/badge/plugins/baek-labs/hames/claude.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
hames 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 today.
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": "hames",
"version": "2.0.0",
"description": "A workspace-first harness for approved, evidence-backed agent work",
"author": {
"name": "Baek Labs",
"url": "https://github.com/baek-labs"
},
"homepage": "https://github.com/baek-labs/hames",
"repository": "https://github.com/baek-labs/hames",
"license": "MIT",
"keywords": ["agents", "harness", "contracts", "verification"]
}
What it installs
The manifest is a name and a version. 4 skills, 3 hooks travel with it, and installing the plugin installs all of them — 68 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.
- today First seen · 14 lines scan A 242c4bdbbc19
hames is a plugin published in the GitHub repository baek-labs/hames (5 stars, last pushed yesterday), 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-04.
Other plugins, from other repositories
software-factory
Lanes, tickets, and a human merge. Same skills as Cursor, Grok, and Codex.
dev-workflow
Plan features with structured PRDs, checkpoint progress, and resume across sessions.
manager
Product and project management discipline for the NVZver marketplace. Agents: product-manager — shapes vague ideas into structured draft pitches and returns their full content + pending human gates (writes no files); project-manager — stewards the roadmap, recommends what to build next with dependency/risk/value…
ravenclaw
Personal work context management for AI-powered development. Track epics, issues, wiki pages, and knowledge ontology across AI agent sessions.
orchestrate
Decompose a large goal into a tree of parallel workers running in isolated git worktrees, collect typed handoffs, replan, repeat until terminal. Idiomatic Claude Code realization of Cursor /orchestrate.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.