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/proticom/gnosys/maintaingit clone --depth 1 https://github.com/proticom/gnosysWhat 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.00000 | $0.00341 |
| Opus 5 | $0.00000 | $0.00170 |
| Sonnet 5 | $0.00000 | $0.00068 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
maintain 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
gnosys maintain
Run vault maintenance: detect duplicates, apply confidence decay, and consolidate similar memories.
Usage
gnosys maintain
gnosys maintain --dry-run
gnosys maintain --auto-apply
Options
| Option | Description |
|---|---|
--dry-run |
Show what would change without modifying anything |
--auto-apply |
Automatically apply all changes (no prompts) |
Behavior
- Resolves configured stores via the project resolver.
- Loads config from the primary store path.
- Runs
GnosysMaintenanceEngine.maintainwith dry-run/auto-apply options. - Prints log messages and progress updates during maintenance.
- Prints a blank line, then
formatMaintenanceReport(report).
Log levels
- warn — printed to stderr with a warning prefix
- action — printed with an action prefix
- info — printed as plain log lines
Progress output
[3/5] scanning duplicates...
Errors
No stores configured:
No Gnosys stores found. Run gnosys init first.
Exits with code 1.
Validation
cd gnosys-public
npm run cli -- maintain --help
npx vitest run src/test/maintain-command-handler.test.ts
Related commands
gnosys stale— find memories not touched recently.gnosys prune— remove archived or stale data.gnosys doctor— diagnose store and config health.
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 · 63 lines · 0 tokens per session scan A c4e9bd25cd51
maintain is a command published in the GitHub repository proticom/gnosys (4 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 341 tokens. 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
init-project
Configure this project for Obsidian PKM — connects the repo to a vault project folder and writes CLAUDE.md integration directives.
setup
Configure Vault PKM plugin — set vault path, API keys, and verify setup.
build
Run full verification pipeline.
generate-rules
Generate development rules and standards into RULES.md.
feedback
File a plugin-capability-gap note, or flush queued notes to GitHub issues.
prd
Generate a Product Requirements Document for an team squad. Business-facing artifact. Sensors and evals gate.