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/recallgit 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.00558 |
| Opus 5 | $0.00000 | $0.00279 |
| Sonnet 5 | $0.00000 | $0.00112 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
recall 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gnosys recall
Return relevant memories as injectable context for agents and hosts.
Usage
gnosys recall "auth tokens"
gnosys recall "auth tokens" --host
gnosys recall "auth tokens" --json
gnosys recall "auth tokens" --federated --scope project,user
gnosys recall "auth tokens" --aggressive --trace-id my-trace-001
Options
| Option | Description |
|---|---|
--limit <n> |
Max memories to return (default from config, federated default 10) |
--aggressive |
Force aggressive mode (inject medium-relevance memories) |
--no-aggressive |
Force filtered mode (hard cutoff at minRelevance) |
--trace-id <id> |
Trace ID for audit correlation (legacy path) |
--json |
Output raw JSON |
--host |
Host-friendly <gnosys-recall> XML-like format |
--federated |
Federated search with tier boosting |
--scope <scope> |
Filter scopes: project, user, global (comma-separated) |
-d, --directory <dir> |
Project directory for federated context |
Federated path
When --federated or --scope is set:
- Opens central DB; exits if unavailable.
- Calls
federatedSearchwith project detection and scope filter. - Outputs recall-like JSON structure,
<gnosys-recall>host format, or human list.
Legacy path (default)
When not using federated/scope:
- Creates
GnosysResolver, resolves stores; exits if none. - Initializes audit via
initAudit(storePath). - Loads config and merges aggressive override from CLI flags.
- Builds search index and calls
recall(query, ...). - Outputs JSON,
formatRecall(host), orformatRecallCLI(human). - Closes audit via
closeAudit().
Output formats
- JSON — structured recall result (legacy) or federated memory list
- Host (
--host) —<gnosys-recall>wrapper for MCP/host injection - CLI default — human-readable formatted recall block
Validation
cd gnosys-public
npm run cli -- recall --help
Related commands
gnosys discover/gnosys search— browse without recall formatting.gnosys ask— LLM synthesis over retrieved memories.
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 · 65 lines · 0 tokens per session scan A 527a17bc8330
recall 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 558 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.