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 skills/baek-labs/hames/source-command-archivenpx skills add baek-labs/hames --skill source-command-archivegit clone --depth 1 https://github.com/baek-labs/hamesWhat 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.00142 |
| Opus 5 | $0.00012 | $0.00071 |
| Sonnet 5 | $0.00005 | $0.00028 |
| Haiku 4.5 | $0.00002 | $0.00014 |
Grade A, and why
source-command-archive 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
source-command-archive
Use this skill when the current user invokes /archive <task-id> for an accepted contract.
node arsenal/task_contract.js archive --workspace "<workspace-path>" --task-id "<task-id>"
The helper moves the package from .hames/contracts/_Active/ to the same workspace's .hames/contracts/_Archive/ and records ARCHIVED. This is a separate, recoverable archive transition, not deletion. Report the archived path. Do not commit, push, or deploy automatically.
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 · 15 lines · 23 tokens per session scan A 670ed3a712f5
source-command-archive is a skill published in the GitHub repository baek-labs/hames (5 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 142 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 skills, from other repositories
b3os-team-inbox
Skill "b3os-team-inbox" from b3rys/b3rys-team-os, covering b3os-team-inbox, 언제 쓰는가, 자기 id 자동 감지, 사용 예 and inbox 확인.
b3os-task-mgmt
Deprecated compatibility stub. Use b3os-task-loop for Tasks 칸반, 주행모드, handoff, continuation guard, review-wait, scheduled workloop.
legion-implement
Deliver an issue end-to-end through scoped implementation, verification, and pull-request readiness.
to-prd
Turn the current conversation context into a PRD and write it to .context/prd/ so it can be sliced into iudex tickets. Use when the user wants to create a PRD from the current context.
to-issues
Break a plan, spec, or PRD into independently-grabbable iudex tickets using tracer-bullet vertical slices, and register them in the iudex queue with their dependencies. Use when the user wants to convert a plan into tickets, create implementation tickets, or break down work into the iudex queue.
apm-issue-autopilot
Use this skill to drive any open microsoft/apm issue (bug, feature, docs, refactor, perf) from raw intake to a mergeable PR with triage as the central, paramount gate. Run the apm-triage-panel rubric per issue first, then present ONE consolidated triage review for the whole batch and escalate to the maintainer BY…