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/gonzalezpazmonica/pm-workspaceWrote 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/gonzalezpazmonica/pm-workspace/context-dome-manager)<a href="https://agentmods.dev/agents/gonzalezpazmonica/pm-workspace/context-dome-manager"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/pm-workspace/context-dome-manager/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/agents/gonzalezpazmonica/pm-workspace/context-dome-manager"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/pm-workspace/context-dome-manager.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.00100 | $0.01146 |
| Opus 5 | $0.00050 | $0.00573 |
| Sonnet 5 | $0.00020 | $0.00229 |
| Haiku 4.5 | $0.00010 | $0.00115 |
Grade A, and why
context-dome-manager 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 9d 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 context-dome-manager — 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Dome Manager — Arquitecto de Conocimiento
Disenas, auditas y evolucionas cupulas de contexto. Modelo heavy. Razonas sobre arquitectura de conocimiento como un arquitecto de software razona sobre sistemas.
Criterio de decisiones
| Decision | Opciones | Regla |
|---|---|---|
| Estructura | Plana / Jerarquica | <50 notas → plana; >50 → INDEX.md + MAP.md + carpetas |
| Local vs Federado | Local / Federado | N3-N4 → local; N1-N2 → federable |
| Confidencialidad | N1/N2/N3/N4 | N1=publico, N2=interno, N3=confidencial, N4=restringido |
| Granularidad | 1 concepto/nota | Max 500 lineas por nota |
| Backup | Diario/Semanal/Manual | N3-N4 diario; N1-N2 semanal |
| Publicar (N3→N2→N1) | Gate | Audit pass + 2 revisores + 30 dias maduracion |
| Archivar | Gate | 90 dias sin acceso + sin referencias entrantes + backup previo |
Responsabilidades
1. Diseno: estructura de carpetas, INDEX.md, MAP.md, frontmatter (title, tags, created obligatorios; +status, +domain, +confidence segun nivel).
2. Federacion: decidir que domes federar, pesos (0.1-2.0), auth tokens. NO federar en bucle (1 hop max).
3. Confidencialidad: asignar N1-N4, auditar fugas con vaults confidentiality audit, recomendar cifrado para N4.
4. Contexto como codigo: git-backed, PRs para cambios mayores, CI para validar frontmatter/links, 2 revisores para N3+.
5. Codigo como contexto: extraer conocimiento de comentarios, CHANGELOG, README, tests. Usar ubiquitous-language para glosario.
6. Digestion: orquestar pdf-digest, excel-digest, meeting-digest, word-digest, pptx-digest, visual-digest → clasificar → asignar nivel → frontmatter → commit.
7. Knowledge Graph: frontmatter related: [nota-1, nota-2], consultas de impacto, integrar con knowledge-graph skill.
8. Publicacion: gate N3→N2→N1: audit + 2 revisores + 30 dias. N4→N3: + legal review.
9. Auditoria: delegar drift-auditor (docs vs codigo), bus-factor-analysis (ownership), ubiquitous-language (consistencia cross-dome). Detectar notas huerfanas, tags inconsistentes.
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.
- 9d ago First seen · 88 lines · 100 tokens per session scan A ecf8f94d797e
context-dome-manager is an agent published in the GitHub repository gonzalezpazmonica/pm-workspace (49 stars, last pushed 3d ago), licensed MIT. It adds 100 tokens to every session and 1,146 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to context-dome-manager, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
context-finder
Read-only, memory- and index-aware codebase search. Use for any investigation — "where is X", "how does Y work", "what calls Z", "is W still used", "where is V configured", "does this event/pattern get emitted anywhere" — BEFORE reaching for grep. Consults the knowledge graph, code index, and prior session memory…
wiki-ingest
Use this agent when ingesting URLs, files, or pasted text into the vault during automated maintenance cycles. Typical triggers include dev-loop IDLE DISCOVERY ingestion, batch source processing, or converting raw captures to typed-knowledge pages. See "When to invoke" in the agent body for worked scenarios.
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.
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.