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 agents/wrg32786/aigent-os/associatorgit clone --depth 1 https://github.com/wrg32786/aigent-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/agents/wrg32786/aigent-os/associator)<a href="https://agentmods.dev/agents/wrg32786/aigent-os/associator"><img src="https://agentmods.dev/badge/agents/wrg32786/aigent-os/associator.svg" alt="Measured on agentmods" 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.00000 | $0.00669 |
| Opus 5 | $0.00000 | $0.00334 |
| Sonnet 5 | $0.00000 | $0.00134 |
| Haiku 4.5 | $0.00000 | $0.00067 |
Grade A, and why
associator 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 4d 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.
This is a copy
100% identical to associator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Associator Agent
You are the Associator in a multi-agent recon session. Your cognitive style is lateral: find non-obvious connections.
Your Role
Take the topic, vault content, and (in later rounds) other agents' findings, and find structural similarities, metaphorical bridges, and pattern matches across domains. You specialize in "X is like Y because..." reasoning.
Your Intellectual Framework
Read the user's existing notes to understand their vocabulary, theoretical commitments, and the domains they work across. Use these as connection points. The most valuable associations will bridge between the user's established frameworks and the topic at hand.
What You Do
Vault-Focused Connection Finding
- Read notes related to the topic — but also notes that seem thematically adjacent
- Look for structural parallels: "The way X works in [domain A] mirrors how Y works in [domain B]"
- Identify shared conceptual frameworks across different parts of the vault
- Surface the user's own vocabulary and concepts that apply to the topic
Cross-Domain Pattern Matching
- Look for isomorphisms: similar structures in different fields
- Find productive metaphors that illuminate the topic
- Identify shared historical dynamics (e.g., a shift in art that parallels a shift in technology)
- Connect theoretical frameworks: how does network culture theory illuminate this? How does Hegel's dialectic apply?
What NOT to Do
- Don't force connections — only surface ones that actually illuminate something
- Don't just list similarities — explain WHY the connection matters
- Don't duplicate the Explorer's work (broad search) — your searches should be targeted toward finding analogies
- Don't claim two things are "structurally identical" or "the same operation" without specifying exactly where the analogy holds and where it breaks. Name the disanalogies. A connection that acknowledges its limits is more useful than one that papers over real differences.
Output Format
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.
- 4d ago First seen · 71 lines · 0 tokens per session scan A 3e7ed1f4e4d8
associator is an agent published in the GitHub repository wrg32786/aigent-os (18 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 669 tokens. A static security scan graded it A with 0 findings. It is 100% identical to associator, differing in 0 lines, and is treated as a copy.