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 agentmods add commands/baek-labs/hames/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/commands/baek-labs/hames/index)<a href="https://agentmods.dev/commands/baek-labs/hames/index"><img src="https://agentmods.dev/badge/commands/baek-labs/hames/index.svg" alt="Measured on agentmods" 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 | $0.00023 | $0.01018 |
| Opus 5 | $0.00012 | $0.00509 |
| Sonnet 5 | $0.00005 | $0.00204 |
| Haiku 4.5 | $0.00002 | $0.00102 |
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 3d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/index
사용법: /index / /index <target> (target 은 alias 또는 경로)
본 커맨드의 정체
/index는 진단 전용 도구다. 자동 수정은 하지 않는다.
스크립트는 JSON 리포트만 출력하며, 모든 수정은 별도 단계로 CEO 승인을 거쳐 수동 적용된다.
HamesSystem 규칙 구조 점검은 /doctor 담당.
진단 항목 (스키마: index-2026-05-08)
공통 (모든 tier):
- 프론트매터 완결성 (Related / Topic / Type / tags) + 필드 순서
- 값 일관성 인벤토리
- 푸터 (
## 관련노트) 존재 여부 - 중복 의심 파일 (날짜 접두사 제거 후 동일 파일명)
- 위키링크 검증
추가 (tier=deep 워크스페이스만):
- 인덱스 미등재 고아 파일 / 임시 파일 / 아카이브 후보 (60일+) /
_Index.md누락
Tier 결정 규칙
- deep:
workspaces/Investment,workspaces/Business,workspaces/Company,workspaces/Hobby. 그리고 워크스페이스 루트에_Index.md가 있는 워크스페이스(예: ). - light: 그 외. frontmatter / footer / duplicates / wikilinks / value_inventory 만 검사.
각 워크스페이스 리포트의 tier 필드에 적용 모드가 표기된다.
Step 1 — 스캔 실행
인수 없음 또는 --all → 전체 진단
python arsenal/manager.py
# 또는
python arsenal/manager.py --all
.claude/workspace_paths.json 의 등록된 모든 워크스페이스(존재하는 것만) +
arsenal/ 도구 레지스트리(arsenal_registry_audit) 점검.
중첩된 child 워크스페이스(예: nested-project/sub-app)는 부모 스캔에서 제외하여 중복 집계 방지.
특정 워크스페이스 지정
python arsenal/manager.py <target>
target 으로 허용되는 형태:
- alias (대소문자 무시): 워크스페이스 이름의 다양한 표기
- 상대 경로:
workspaces/Company,nested-project/sub-app - 절대 경로
Step 2 — 에이전트 분석 (Semantic Analysis)
출력된 **HAMES SYSTEM AUDIT REPORT (JSON)**를 분석:
| 항목 | JSON 필드 | 비고 |
|---|---|---|
| 프론트매터 이슈 | missing_frontmatter |
필드 누락 + 순서 오류 |
| 푸터 누락 | footer_missing |
## 관련노트 미존재 |
| 값 인벤토리 | value_inventory |
비일관 값 탐지용 전체 현황 |
| 고아 파일 | orphaned_files |
_Index.md 미등재 (deep only) |
| 임시 파일 | temp_files |
즉시 삭제 제안 가능 (deep only) |
| 아카이브 후보 | archive_candidates |
CEO 승인 후 이동 (deep only) |
| 인덱스 누락 | missing_indexes |
워크스페이스에 _Index.md 없음 (deep only) |
| 중복 의심 | potential_duplicates |
CEO 단일화/삭제 결재 요청 |
| 링크 검증 | links_found_for_agent_verification |
에이전트가 경로·워크스페이스 직접 확인 |
프론트매터 이슈 예시:
Missing: tags— tags 필드 없음Wrong order: found ['Type', 'Related'], expected ['Related', 'Type']— 순서 오류
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.
- 3d ago First seen · 93 lines · 23 tokens per session scan A 4830edb0b8a1
index is a command published in the GitHub repository baek-labs/hames (5 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 1,018 once invoked, about $0.0001 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-08-31.
Other commands, from other repositories
om-incident-capture
Capture an incident from Slack channels, DMs, and threads into structured vault notes. Produces a complete incident work note with timeline, people, analysis, and brag doc entry.
create-plan
This document describes the requirements for an execution plan ("ExecPlan"), a design document that a coding agent can follow to deliver a working feature or system change. Treat the reader as a complete beginner to this repository: they have only the current working tree and the single ExecPlan file you provide.…
is-not-duplicated
please investigate the codebase based on your changes - do we have code duplication? After analysis, write updates to DUPLICATIONREPORT.md with the results. Keep in mind that other agents could keep their records, so you need to check the document first, decided to update or add new information.
wtfp:export-latex
Export the manuscript and bibliography to portable LaTeX source with declared formatting.
assess
Run an AI literacy assessment — scan the repo for evidence, ask clarifying questions, produce a timestamped assessment document, apply immediate habitat fixes, recommend workflow changes, capture a reflection, and add a literacy level badge to the README.
wb-datacore-query
Load directions via mcpwork-buddywbrun("agentdocs", {"path": "obsidian/datacore-query-directions", "depth": "full"}), then run mcpwork-buddywbrun("datacoreschema") first.