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/rna4219/memx-core/knowledgegit clone --depth 1 https://github.com/RNA4219/memx-coreWhat 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.00243 |
| Opus 5 | $0.00000 | $0.00121 |
| Sonnet 5 | $0.00000 | $0.00049 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
knowledge 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.
What it actually says
Add Knowledge
Add a knowledge base entry to memx knowledge store.
Usage
/knowledge --scope <scope> <knowledge content>
Required Arguments
--scope: Working scope (e.g.,glossary,patterns,architecture)
Optional Arguments
--pinned: Pin the knowledge for quick access
What it does
- Creates a knowledge entry with the specified working scope
- Knowledge entries are time-independent facts, definitions, policies
- Can be pinned for quick reference
Example
/knowledge --scope glossary typed_ref format: memx:{type}:{provider}:{id}
/knowledge --scope architecture --pinned memx uses 4 SQLite stores: short, journal, knowledge, archive
Implementation
Use the Bash tool to run:
cd C:/Users/ryo-n/Codex_dev/memx-core/memx_spec_v3/go && go run ./cmd/mem in knowledge --title "<auto-generated title>" --body "<knowledge content>" --scope "<scope>" [--pinned] --sensitivity internal
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 · 41 lines · 0 tokens per session scan A b090f0412312
knowledge is a command published in the GitHub repository RNA4219/memx-core (23 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 243 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-30.
Other commands, from other repositories
gh-triage
GitHub OSS maintainer lifecycle triage, review, and approval management.
changeset
../../.mastracode/commands/changeset.md.
commit
../../.mastracode/commands/commit.md.
critique-pr
../../.mastracode/commands/critique-pr.md.
document
../../.mastracode/commands/document.md.
gh-bulk-issues
../../.mastracode/commands/gh-bulk-issues.md.