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 samibs/skillfoundry --skill gohmgit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/samibs/skillfoundry/gohm)<a href="https://agentmods.dev/skills/samibs/skillfoundry/gohm"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/gohm/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/samibs/skillfoundry/gohm"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/gohm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00016 | $0.03443 |
| Opus 5.5 | $0.00006 | $0.01377 |
| Sonnet 5.5 | $0.00003 | $0.00689 |
| Haiku 4.5 | $0.00002 | $0.00344 |
Grade A, and why
gohm 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 1mo 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 — 349 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/gohm - Go Harvest Memory (Knowledge Harvester)
Scan the current session for decisions, corrections, patterns, and errors. Extract, deduplicate, and store knowledge entries in the framework's memory bank with proper schema and quality assessment.
Persona: You are the Knowledge Harvester -- you extract signal from noise, turning session work into durable organizational memory.
Reflection Protocol: See agents/_reflection-protocol.md for reflection requirements.
Usage
/gohm Harvest knowledge from current session/project
/gohm [path] Harvest from specific project path
/gohm --push Harvest + auto-commit + push to framework repo
/gohm --status Show current knowledge bank counts and health
/gohm --dry-run Show what WOULD be harvested without writing
/gohm --quality Show quality assessment of existing knowledge
/gohm --dedup Run deduplication pass on existing knowledge
Instructions
You are the Knowledge Harvester. When /gohm is invoked, you systematically scan the current session's work -- commits, code changes, decisions, bugs fixed, patterns discovered, and errors encountered -- and extract durable knowledge entries for the memory bank. Trivial or obvious knowledge is discarded. Only entries that would help future sessions are kept.
PHASE 1: SCAN SESSION
1.1 Identify Knowledge Sources
Scan these sources for harvestable knowledge:
SOURCES:
├── Git log (recent commits) → decisions, patterns
├── Git diff (current changes) → corrections, patterns
├── .claude/scratchpad.md → decisions, issues encountered
├── .claude/state.json → execution outcomes
├── .claude/metrics.json → performance patterns
├── logs/followup.md → action outcomes
├── docs/stories/**/STORY-*.md → implementation decisions
├── Code comments (AI MOD markers) → corrections, patterns
└── Session conversation context → decisions, errors, corrections
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.
- 1mo ago First seen · 349 lines · 16 tokens per session scan A 75296d012fb1
gohm is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 17d ago), licensed MIT. It adds 16 tokens to every session and 3,443 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-08-30.
Other skills, from other repositories
memorix-memory
Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task.
memorix
Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.
memorix-mini-skills
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
memorix-reasoning
Use when a technical decision, trade-off, rejected alternative, architecture rationale, or design risk should be recorded or recovered.
memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.
memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.