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/theagenticguy/opencodehub/doc-behavior-processesgit clone --depth 1 https://github.com/theagenticguy/opencodehubWhat 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.01485 |
| Opus 5 | $0.00000 | $0.00743 |
| Sonnet 5 | $0.00000 | $0.00297 |
| Haiku 4.5 | $0.00000 | $0.00148 |
Grade A, and why
doc-behavior-processes 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.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Packet · {{ repo }} · behavior/processes.md
1. Objective
Produce {{ docs_root }}/behavior/processes.md: one H2 per top process in {{ repo }}, each with a numbered step list citing path:LOC on every line, entry-point attribution (HTTP route / MCP tool / CLI command / scheduled job), and a ### Related subsection with backtick citations to handler files.
2. Scope
- Create:
{{ docs_root }}/behavior/processes.md - Do not touch:
{{ docs_root }}/behavior/state-machines.md, any other file under{{ docs_root }}/, any source file in the repo,.context.md,.prefetch.md, or any.packets/*.mdother than this one.
3. Input specification
| Source | Read how | Cache state |
|---|---|---|
| Shared context | Read {{ context_path }} |
always first |
| Prefetch ledger | Read {{ prefetch_path }} |
always first |
| Top processes | {{ context_path }} § Top processes |
cached |
| Route inventory | {{ prefetch_path }} § route_map |
cached |
| MCP tool inventory | {{ prefetch_path }} § tool_map |
cached |
| Step sequence per process | mcp__codehub__context({symbol: <process-name>}) |
mid-run |
| Disambiguation lookup | mcp__codehub__query({text: "<process name>"}) |
mid-run, only on collision |
4. Process
Read {{ context_path }}andRead {{ prefetch_path }}. Confirm the Top processes list is present; if empty, follow Fallback paths.- Select the top 8 processes from
.context.md § Top processes(ranked bystep_count). - For each of the 8: call
mcp__codehub__context({symbol: <process-name>})to pull entry point, ordered outbound calls, and handler files. Cache the per-process digest in this packet's Work log. - Group each process by its initiator using the cached
route_map/tool_mapdigest: HTTP route, MCP tool, CLI command, scheduled job, or internal. - Draft
processes.mdwith H1 ={{ repo }} · Processes. One H2 per process (max 8). Under each H2: a single-lineEntry point: <path:LOC>, a numbered step list where every step citespath:LOC, then a### Relatedsubsection listing the top 3-6 handler/helper files as backtick citations. - Processes with fewer than 3 concrete steps collapse into a trailing
## Minor flowsH2 (one bullet per flow, not an H2 section of their own). Write {{ docs_root }}/behavior/processes.md.
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 · 104 lines · 0 tokens per session scan A ad973bfd0846
doc-behavior-processes is an agent published in the GitHub repository theagenticguy/opencodehub (3 stars, last pushed 20d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,485 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.