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/khou/gardenkit/garden-capturenpx skills add khou/gardenkit --skill garden-capturegit clone --depth 1 https://github.com/khou/gardenkitWrote 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/khou/gardenkit/garden-capture)<a href="https://agentmods.dev/skills/khou/gardenkit/garden-capture"><img src="https://agentmods.dev/badge/skills/khou/gardenkit/garden-capture.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.00080 | $0.00438 |
| Opus 5 | $0.00040 | $0.00219 |
| Sonnet 5 | $0.00016 | $0.00088 |
| Haiku 4.5 | $0.00008 | $0.00044 |
Grade A, and why
garden-capture 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 5d 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
garden-capture
Drops a raw capture into ~/garden/inbox/. The gardener (scheduled) processes inbox files into properly-filed atomic notes.
When to use
Only when the user explicitly invokes capture. Triggers: "capture this", "save that", "for the garden", "remember X", or equivalents.
If you notice something in conversation that seems noteworthy but the user didn't ask to capture, do not write to inbox/. Suggest it inline ("worth capturing?") and let the user decide. The vault is the user's, and they want explicit control over what goes in.
How
- Compose a short markdown file with this structure:
---
type: capture
created: <YYYY-MM-DD>
source: <session | manual | conversation>
---
# <one-line summary>
<the content: keep it raw, gardener will refine>
Context: <project | person | topic if known>
-
Filename:
~/garden/inbox/<YYYY-MM-DD>-<slug>.md. Slug = first 5–7 words of the summary, lowercased, hyphenated. -
Write the file. Don't edit anything else in the vault: that's the gardener's job.
-
Tell the user one line: "Captured to inbox as
<filename>."
Multiple captures
If the user dumps several distinct things at once, write each as a separate inbox file. One concept per file.
Don't
- Don't file directly into
notes/,decisions/, etc.: that's gardener territory. - Don't add wiki-links speculatively. Gardener handles linking.
- Don't ask for permission for routine captures. Just write.
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.
- 5d ago First seen · 49 lines · 0 tokens per session scan A 4b5ddc1fd57c
garden-capture is a skill published in the GitHub repository khou/gardenkit (4 stars, last pushed 3mo ago), licensed MIT. It adds 80 tokens to every session and 438 once invoked, about $0.0004 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
context-manager
Use when a long-running agent task needs context budgeting, checkpointing, compaction, retrieval, or capability-based model routing.
knowledge-ops
Use when an Obsidian knowledge system needs classification, deduplication, retrieval, synchronization, debt queues, or governed Agent/Wiki promotion.
session-learn
Use when a completed work session should yield durable concepts, corrections, decisions, reusable patterns, and a traceable next action.
moradin-learn-from-sessions
Extract user preferences from accumulated Claude Code session history. One-time bootstrap that mines your past corrections, preferences, and lessons into reviewable candidates.
moradin-audit
Lint memory — find stale files, missing frontmatter, bad topic tags, orphans. Propose fixes.
moradin-recall
Search memory and synthesize an answer with citations to source files.