Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add sk-lim19f/Hypomnema/plugin install hypoWrote 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/sk-lim19f/hypomnema/lint)<a href="https://agentmods.dev/commands/sk-lim19f/hypomnema/lint"><img src="https://agentmods.dev/badge/commands/sk-lim19f/hypomnema/lint.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.1 | $0.00035 | $0.00690 |
| Opus 5 | $0.00017 | $0.00345 |
| Sonnet 5 | $0.00007 | $0.00138 |
| Haiku 4.5 | $0.00003 | $0.00069 |
Grade A, and why
lint 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running /hypo:lint. Validate all wiki pages for frontmatter correctness and broken [[wikilink]] references.
What this checks
- Every
.mdfile underpages/andprojects/should have frontmatter (missing frontmatter is a warning) - Required fields:
title,type typemust be one of the recognised values (concept, source-summary, learning, adr, …)updatedfield should be present- All
[[wikilinks]]must resolve to an existing page slug
Step 1 — Run script
Bundled scripts here run via ${CLAUDE_PLUGIN_ROOT}/scripts/. To resolve that package root: if ${CLAUDE_PLUGIN_ROOT} is already an absolute path, use it; otherwise read pkgRoot from ~/.claude/hypo-pkg.json (only when non-empty and the target script exists under it); otherwise use the hypo@hypomnema (or legacy hypomnema@hypomnema) installPath in ~/.claude/plugins/installed_plugins.json; if none resolve, stop and tell the user to run hypomnema upgrade --apply (or /hypo:upgrade on a plugin install) or reinstall instead of guessing the cache layout.
If the user specified a Hypomnema directory, pass it as --hypo-dir="<path>". Otherwise omit the flag and the script resolves the Hypomnema root automatically via HYPO_DIR → hypo-config.md scan → ~/hypomnema.
Step 2 — Run lint
node ${CLAUDE_PLUGIN_ROOT}/scripts/lint.mjs [--hypo-dir="<path>"] [--json] [--fix]
Options:
--json— output results as JSON (useful for tooling)--fix— auto-add missingupdatedfield (safe repairs only; no other fields are modified)
Show the output verbatim.
Step 3 — Interpret results
✓ No lint issues found— Hypomnema is clean✗ <file>: <message>— error (missing required field or malformed frontmatter); must be fixed⚠ <file>: <message>— warning (unknown type, missingupdated, broken link); worth fixing
A non-zero exit code means at least one error was found (warnings alone do not produce a non-zero exit code).
Step 4 — Offer to fix
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 Changed f52e2bf291cc
- 7d ago First seen · 56 lines · 35 tokens per session scan A f256ddf17293
lint is a command published in the GitHub repository sk-lim19f/Hypomnema (10 stars, last pushed 3d ago), licensed MIT. It adds 35 tokens to every session and 690 once invoked, about $0.0002 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.