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/kouroshez/coding-os/memory-searchgit clone --depth 1 https://github.com/kouroshez/coding-osWhat 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.00393 |
| Opus 5 | $0.00000 | $0.00197 |
| Sonnet 5 | $0.00000 | $0.00079 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
memory-search 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
Search agent memory + learned patterns for cross-session context relevant to $ARGUMENTS.
Use during the Orient phase of the Core Loop (../skills/thinking_os/SKILL.md) — never as a substitute for reading current code, only as a prefetch for "have I solved this before?".
Steps:
- If
$ARGUMENTSis empty, ask the user what to search for. - Call
cos_search(query=$ARGUMENTS, min_confidence=0.3, since_days=180, limit=10). - If 0 hits: try
cos_doc_search(query=$ARGUMENTS, limit=5)(escalate to docs layer per ../rules/memory.md routing). - If still 0 hits: tell the user "no prior context — this looks new" and suggest a fresh
Skill thinking_osCynefin classification. - If hits exist, render:
## Memory search — "{query}" ### Top patterns ({n}) 1. [{confidence}] {title} Type: {memory_type} | Impact: {impact_score} | Last seen: {date} Summary: {short} Source: {cos_details tool call to fetch full body} - For each hit ≥ 0.7 confidence: offer to invoke
cos_details(id=...)to expand. - Verify before recommending (per ../rules/memory.md): if a high-confidence pattern names a file or function, confirm it still exists in the repo before quoting it as authoritative.
Memory-hygiene reminder: this is a read operation. If during the work you confirm a pattern was useful, record back via cos_observation_record so the next session benefits.
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 · 24 lines · 0 tokens per session scan A e06943abc5f0
memory-search is a command published in the GitHub repository kouroshez/coding-os (6 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 393 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
export
Export a knowledge abstract to an Obsidian vault — a folder of Markdown notes linked by [[wikilinks]].
info
Display information and statistics about a knowledge abstract.
wh:llmsr-transfer
Use when the user wants to test whether an LLM-SR discovered equation's FORM generalizes to a recording the search never scored, and ingest both transfer numbers into the Wheeler knowledge graph.
wh:resume
Use when starting a new session and restoring Wheeler context from STATE.md or .plans/.continue-here.md.
maestro-next
Unified entry for all development intents — classify intent, assess complexity, route to the correct execution channel: /maestro-companion (lightweight), standard single run, or /maestro and /maestro-ralph (multi-step manual/orchestrated). Pure router, never runs execution loops itself.
analyze-task
Parse user task description -> detect required capabilities -> build dependency graph -> design dynamic roles with role-spec metadata. Outputs structured task-analysis.json with frontmatter fields for role-spec generation.