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.
git clone --depth 1 https://github.com/conorbronsdon/agent-context-osWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/conorbronsdon/agent-context-os/find-context)<a href="https://agentmods.dev/commands/conorbronsdon/agent-context-os/find-context"><img src="https://agentmods.dev/badge/commands/conorbronsdon/agent-context-os/find-context/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/conorbronsdon/agent-context-os/find-context"><img src="https://agentmods.dev/badge/commands/conorbronsdon/agent-context-os/find-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00033 | $0.00598 |
| Opus 5.5 | $0.00013 | $0.00239 |
| Sonnet 5.5 | $0.00007 | $0.00120 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
find-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 1mo 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/find-context — Find Relevant Files by Topic
Find and load the right context files for any topic, even when it spans multiple domains.
Instructions
1. Get the topic
The user will say /find-context <topic> (e.g., /find-context auth rewrite, /find-context q3 planning). This avoids colliding with Claude Code's built-in /context command.
2. Search (three strategies, in parallel)
Tag match — use Grep to search Markdown files for the topic in YAML
tags: frontmatter (the strongest signal—the file was explicitly categorized).
Filename match — Glob for files with the topic keyword in their name.
Header match — Grep for # /## headings containing the topic across .md files. Skip sessions/ (unless the topic is from the last 3 days), node_modules/, and any vendored docs.
3. Rank and present
Combine, deduplicate, and rank by signal strength:
- Tag matches (highest — explicitly categorized)
- Filename matches
- Header matches (lowest — may be incidental)
Present a ranked list with the match type and line count:
CONTEXT FILES for "[topic]":
[tag] path/to/file.md — [first line or description] ([N] lines)
[name] path/to/file.md — [first line or description] ([N] lines)
[hdr] path/to/file.md — [first line or description] ([N] lines)
Load all? (or specify which by number)
4. Load selected files
Read the selected files and give a one-line summary of what each contains relative to the topic. If more than 3 are selected, read only the first 30 lines of each and offer to load full content on request.
Tag Convention
Context files (not skills or commands) can carry a tags: line in YAML frontmatter so /find-context can find them by category rather than by incidental keyword:
---
tags: [auth, security, backend]
---
Tags are lowercase, short, and descriptive. Group them however fits your work — for example:
- Domains: the areas you work in (
backend,marketing,research) - Topics: recurring subjects (
auth,pricing,onboarding) - Types: the kind of doc (
strategy,reference,planning)
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.
- 1mo ago Changed 2c817844129b
- 2mo ago First seen · 63 lines · 33 tokens per session scan A a514daad0b01
find-context is a command published in the GitHub repository conorbronsdon/agent-context-os (30 stars, last pushed 2d ago), licensed MIT. It adds 33 tokens to every session and 598 once invoked, about $0.0001 per session on Opus 5.5. 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
load-context
Load a large file or content into the RLM system for chunk-based analysis.
budget
View context budget allocation — code vs conversation vs memory breakdown.
load
Load the shared Wingman context for this project.
speckit.memory-md.capture-from-diff
Capture durable knowledge and architecture decisions from current or provided diffs.
style-skill-memory
Generate SKILL memory package from style reference for easy loading and consistent design system usage.
speckit.memory-md.share-lesson
Promote an approved local technical/architectural lesson from docs/memory into the global shared memory.