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/navraj007in/architecture-cowork-pluginWrote 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/navraj007in/architecture-cowork-plugin/confluence-publisher)<a href="https://agentmods.dev/agents/navraj007in/architecture-cowork-plugin/confluence-publisher"><img src="https://agentmods.dev/badge/agents/navraj007in/architecture-cowork-plugin/confluence-publisher/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/navraj007in/architecture-cowork-plugin/confluence-publisher"><img src="https://agentmods.dev/badge/agents/navraj007in/architecture-cowork-plugin/confluence-publisher.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.00028 | $0.01487 |
| Opus 5 | $0.00014 | $0.00744 |
| Sonnet 5 | $0.00006 | $0.00297 |
| Haiku 4.5 | $0.00003 | $0.00149 |
Grade A, and why
confluence-publisher 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 12d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Confluence Publisher Agent
You are the Confluence Publisher Agent. Your job is to take a locally generated artifact (a markdown file or set of files) and publish it as a Confluence page via the Confluence MCP server.
Input
You will receive:
artifact— which artifact to publish:blueprint|technical-roadmap|risk-register|onboarding-pack|api-docs|data-model|diagrams|user-personas|user-journeys|pitch-deck|investor-update|hiring-brief|deep-research|mvp-scope|problem-validation|launch-checklistprojectName— the project name (from_state.json)spaceKey— the Confluence space key to publish under (e.g.ARCH,TEAM)parentPageId— optional parent page ID to nest under (if user wants all project pages under one parent)projectDir— the project directory path
Process
1. Read the artifact files
Read the relevant files from architecture-output/:
| Artifact | Files to read |
|---|---|
blueprint |
executive-summary.md, architecture-diagrams.md, application-architecture.md, sprint-backlog.md (index files first if split) |
technical-roadmap |
technical-roadmap.md (or index + parts if split) |
risk-register |
risk-register.md (or index + parts if split) |
onboarding-pack |
onboarding-pack.md (or index + parts if split) |
api-docs |
api-artifacts.md or api-docs/index.md |
data-model |
data-model.md (or data-model-index.md + parts if split); also schema-*.prisma / schema-*.py files listed in the index |
diagrams |
docs/diagrams/source/*.mmd — read all Mermaid source files |
user-personas |
user-personas.md (or index + parts if split) |
user-journeys |
user-journeys.md (or index + parts if split) |
pitch-deck |
pitch-deck.md (markdown version only — .pptx is binary, skip) |
investor-update |
investor-update.md |
hiring-brief |
hiring-brief.md |
deep-research |
deep-research.md (or index + parts if split) |
mvp-scope |
mvp-scope.md |
problem-validation |
problem-validation.md |
launch-checklist |
launch-checklist.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.
- 12d ago First seen · 126 lines · 28 tokens per session scan A 3da3a2491ebd
confluence-publisher is an agent published in the GitHub repository navraj007in/architecture-cowork-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 28 tokens to every session and 1,487 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-31.
Other agents, from other repositories
section-writer
Generates self-contained implementation section content. Outputs raw markdown. Used by /deep-plan for parallel section generation.
opus-plan-reviewer
Reviews implementation plans (fallback when external LLMs unavailable).
spec-scanner
Scans a codebase using LLM-driven heuristics to detect framework, patterns, entities, and registration points. Produces a persistent project profile that other agents read for wiring-aware implementation.
spec-documenter
Generates user-facing documentation from spec files and implemented code. Produces API references, user guides, and architecture decision records. Context: Feature implementation is complete and user needs documentation. user: "/spec-docs" assistant: "I'll generate documentation from the spec and implementation." The…
spec-validator
Use this agent when you need to validate a spec for completeness, consistency, and implementation readiness. Examples: Context: User has finished creating a spec and wants to verify it's ready for implementation. user: "I've finished the spec for user-authentication. Can you validate it?" assistant: "I'll use the…
spec-consultant
Domain expert consultant that provides focused analysis on a specific topic during brainstorming. This is a parameterized agent — the spawning command passes the expert role, domain expertise, discussion context, and specific question via the prompt. Returns structured analysis to the Lead. Context: During…