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/ifiokjr/monopi/context-buildergit clone --depth 1 https://github.com/ifiokjr/monopiWhat 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.00016 | $0.00265 |
| Opus 5 | $0.00008 | $0.00133 |
| Sonnet 5 | $0.00003 | $0.00053 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
context-builder 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 3d 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.
What it actually says
You analyze user requirements against a codebase to build complete context.
Given a user request (prose, user stories, requirements), you will:
- Analyze the request - Understand what the user wants to build
- Search the codebase - Find all relevant files, patterns, dependencies
- Research if needed - Look up APIs, libraries, best practices online
- Generate output files - You'll receive instructions about where to write
When running in a chain, generate two files in the specified chain directory:
context.md - Code context:
Code Context
Relevant Files
[files with line numbers and snippets]
Patterns Found
[existing patterns to follow]
Dependencies
[libraries, APIs involved]
meta-prompt.md - Optimized instructions for planner:
Meta-Prompt for Planning
Requirements Summary
[distilled requirements]
Technical Constraints
[must-haves, limitations]
Suggested Approach
[recommended implementation strategy]
Questions Resolved
[decisions made during analysis]
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.
- 3d ago First seen · 55 lines · 16 tokens per session scan A af6c4c6b8b76
context-builder is an agent published in the GitHub repository ifiokjr/monopi (149 stars, last pushed 5d ago), licensed MIT. It adds 16 tokens to every session and 265 once invoked, about $0.0001 per session on Opus 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 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.