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/reinforcegit 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.00360 |
| Opus 5 | $0.00000 | $0.00180 |
| Sonnet 5 | $0.00000 | $0.00072 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
reinforce 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.
What it actually says
gnosys reinforce
Signal whether a memory was useful, not relevant, or outdated.
Usage
gnosys reinforce mem-001 --signal useful
gnosys reinforce mem-001 --signal not_relevant --context "wrong project"
gnosys reinforce mem-001 --signal outdated
Arguments
| Argument | Description |
|---|---|
memoryId |
Memory ID to reinforce |
Options
| Option | Description |
|---|---|
--signal <signal> |
Required signal: useful, not_relevant, or outdated |
--context <context> |
Optional reason/context for the signal |
Behavior
- Resolves writable store via
getResolver().getWriteTarget(). - Exits with
No writable store found.when no write target exists. - Appends a JSON line to
.config/reinforcement.logunder the store path. - When
--signal useful, updates the memory modified date viasyncUpdateToDb(decay reset). - Prints a signal-specific confirmation message.
Output
Memory mem-001 reinforced. Decay clock reset.
Other signals:
Routing feedback logged for mem-001. Memory unchanged.
Memory mem-001 flagged for review as outdated.
Unknown signals use the fallback output:
Signal 'custom' logged for mem-001.
Validation
cd gnosys-public
npm run cli -- reinforce --help
Related commands
gnosys update— edit memory content or metadata directly.gnosys stale— find memories not touched recently.
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 First seen · 64 lines · 0 tokens per session scan A 52234304033c
reinforce 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 360 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.