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 baek-labs/hames --skill indexgit 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/skills/baek-labs/hames/index)<a href="https://agentmods.dev/skills/baek-labs/hames/index"><img src="https://agentmods.dev/badge/skills/baek-labs/hames/index/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/baek-labs/hames/index"><img src="https://agentmods.dev/badge/skills/baek-labs/hames/index.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00032 | $0.00365 |
| Opus 5.5 | $0.00013 | $0.00146 |
| Sonnet 5.5 | $0.00006 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
index 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 28d 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
Index
Use the user's language. Resolve the configured AI work root and read its configuration. An unconfigured root needs /setup; do not invent folders or rules.
Run the bundled runtime/index.js audit --root <root> (optionally --target <workspace-id-or-relative-path>). With no target, inspect every registered workspace and shared root docs/.
This is a read-only audit. Report the checked and excluded scope, violations, items needing judgment, and unreadable or unsupported items separately. Do not call everything healthy when any judgment or unreadable item remains. For each finding show its path, observed fact, rule, and suggested action. Semantic rules require reading the relevant content; check uncertainty with the user, never pretend a path check proves meaning.
File creation's automatic index update is a separate hook operation. An audit must not repair indexes, move documents, rename files, or delete anything.
For a user-requested index repair, run runtime/index.js plan --root <root>, present the exact proposed index changes, and retain its plan_hash. Only after that repair is authorized, run runtime/index.js apply --root <root> --approved --plan-hash <hash>. This repairs index blocks only; moving or editing the original documents requires a separate specific request. Re-audit afterward. A changed preview must be presented again.
Preserve manual text and links. Report broken manual references instead of silently rewriting them. Indexing failure never authorizes deleting the original file. Shell and external-app changes may only be discovered during the next audit; no background filesystem watcher is installed.
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.
- 28d ago First seen · 19 lines · 32 tokens per session scan A db580e38c459
index is a skill published in the GitHub repository baek-labs/hames (5 stars, last pushed 28d ago), licensed MIT. It adds 32 tokens to every session and 365 once invoked, about $0.0001 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-09-22.
Other skills, from other repositories
client-workspace
Create client folder structure in Drive, share docs, check permissions before calls.
harness
Use when governing a workspace's control plane, code or not — the 01-TOOLS/ tooling layer, the 02-DOCS/ chaos→knowledge wiki, the root Knowledge map. Audits it, migrates legacy XX- folders, scaffolds provider tooling, sweeps the inbox, eats a file the person hands over ("cómete este fichero", "guárdalo en la…
confluence-automation
Automate Confluence page creation, content search, space management, labels, and hierarchy navigation via Rube MCP (Composio). Always search tools first for current schemas.
b3os-report
A team reporting skill that turns approved markdown and HTML reports into entries in an internal reports portal. HTML becomes the main view when available, while markdown remains the source and download version.
b3os-team-inbox
A team message-bus client for sending, receiving, and recalling messages between AI teammates. It also supports replying to a specific message thread and sending final reports to the team lead.
b3os-task-loop
A task-tracking work loop that keeps individual, scheduled, and waiting tasks moving until they are completed, blocked, or awaiting approval.