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/commit-contextgit 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.00569 |
| Opus 5 | $0.00000 | $0.00284 |
| Sonnet 5 | $0.00000 | $0.00114 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
commit-context 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 yesterday.
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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gnosys commit-context
Pre-compaction sweep: extract atomic memories from a conversation or context string, check novelty against existing memories, and commit novel ones to the central DB.
Usage
gnosys commit-context "Decision: use SQLite as source of truth"
gnosys commit-context "Meeting notes with durable decisions..." --dry-run
gnosys commit-context "Architecture notes..." --store project
Options
| Option | Description |
|---|---|
--dry-run |
Show what would be committed without writing |
-s, --store <store> |
Writable store for config/tag registry resolution (project, personal, global) |
--store selects the writable store used for config and tag registry resolution in this command. Committed memories are inserted with the current project context (scope: project); it does not change central DB scope to personal/global in the current implementation.
Behavior
- Store resolution — requires a writable store; exits if none found.
- LLM extraction — uses structuring provider to extract JSON array of candidates (summary, type, search_terms).
- Novelty check — builds search index from active stores; skips candidates that overlap existing memories.
- Commit — for novel candidates, structures via
GnosysIngestionand inserts into central DB (unless--dry-run). - Dry run — prints
WOULD ADDlines without DB writes; summary usesDRY RUNmode label. - Duplicates — prints
SKIPwith overlapping memory title. - Summary —
COMMITTEDorDRY RUNline with candidate/add/skip counts.
Output example
Extracting knowledge candidates from context...
Found 3 candidates. Checking novelty...
➕ ADDED: "Use SQLite as source of truth"
ID: deci-012
⏭ SKIP: "Prefer TypeScript"
Overlaps with: TypeScript as implementation language
COMMITTED: 3 candidates, 1 added, 1 duplicates skipped.
Error cases
- No writable store
- No LLM provider available
- LLM output not valid JSON
- No extractable knowledge (empty candidate array)
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.
- yesterday First seen · 72 lines · 0 tokens per session scan A 068f35e3395b
commit-context is a command published in the GitHub repository proticom/gnosys (4 stars, last pushed 15d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 569 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.
setup-pm-skills
Onboard a new user — find out what they do, recommend the right bundles & top skills, and set up a project CONTEXT.md so every skill is tailored to them.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
study
Runtime entry point for extracting design DNA from a live URL, screenshot, or reference site. Part of the Discovery lifecycle phase.
competitive-landscape
Map the competitive landscape for a market or company.