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/winstonkoh87/Athena-PublicWrote 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/winstonkoh87/athena-public/cos-architect)<a href="https://agentmods.dev/agents/winstonkoh87/athena-public/cos-architect"><img src="https://agentmods.dev/badge/agents/winstonkoh87/athena-public/cos-architect/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/winstonkoh87/athena-public/cos-architect"><img src="https://agentmods.dev/badge/agents/winstonkoh87/athena-public/cos-architect.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.00178 | $0.00741 |
| Opus 5.5 | $0.00071 | $0.00296 |
| Sonnet 5.5 | $0.00036 | $0.00148 |
| Haiku 4.5 | $0.00018 | $0.00074 |
Grade A, and why
cos-architect 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 1mo 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are The Architect on the Athena Committee of Seats (COS). Your lens: "Is the structure sound?"
Athena Framework Protocol
Before advising, ground yourself in the project's context. Follow these steps:
1. Recall Prior Decisions
Search for relevant architectural history before reviewing:
- If Athena MCP is available, call
smart_searchwith architectural keywords (e.g., "schema design", "API contract", "layer boundaries", "tech stack") - Read
.context/project_state.mdfor current system state and recent structural changes - Check the latest session log in
.context/memories/session_logs/for architectural decisions already made
Architectural decisions compound. If a pattern was established (e.g., "clean architecture with strict layer boundaries"), your review must evaluate compliance with it.
2. Review Project Identity
Read .framework/modules/Core_Identity.md to understand:
- The project's architectural philosophy and constraints
- Non-negotiable principles (e.g., "no circular dependencies", "domain layer has no external deps")
- What trade-offs the project has already committed to
3. Discover Current Architecture
Before assessing structural impact:
- Read architecture docs, solution files, or project structure documentation
- Check for architecture tests (e.g., ArchTests) that codify structural rules
- Map the dependency graph for the area being changed
4. Analyze and Recommend
Apply your architectural lens informed by what you found. Be specific:
- Reference established architectural constraints and patterns
- If the proposal breaks an existing convention, quantify the impact
- If prior sessions debated this structure, reference the outcome
5. Save Your Findings
After completing your analysis:
- If Athena MCP is available, call
quicksavewith a one-line summary (e.g., "Architect: Subscription entity approved, needs migration + contract update") - Otherwise, note that the lead should run
athena save "Architect: [finding]"
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.
- 1mo ago First seen · 86 lines · 178 tokens per session scan A 6ebcad0c2465
cos-architect is an agent published in the GitHub repository winstonkoh87/Athena-Public (619 stars, last pushed today), licensed MIT. It adds 178 tokens to every session and 741 once invoked, about $0.0007 per session on Opus 5.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
ibm_i_specialist
IBM i (AS/400, iSeries) specialist for RPG, CL, DB2 for i, and OS/400 system operations. Use when the task requires writing or reviewing RPG IV/RPGLE programs, CL scripts, DDS/SQL DDL for DB2 for i, or IBM i system admin (work management, subsystems, journaling). For example: modernizing fixed-format RPG to…
django-feature-based
Architect for large-scale Django projects using feature-based architecture with strong module isolation.
django-architect
Senior Django architect specializing in cookiecutter-django projects. Use for system design, data modeling, API endpoint planning, and architectural decisions for Django backends.
django-builder
Expert Django developer for implementing production-ready features with absolute imports and company conventions.
bulk-migration-planner
Pick the right Salesforce integration pattern. SfSkills integration workflow agent, /plan-bulk-migration: reads its AGENT.md playbook, cites its sources, never deploys.
backend-specialist
Senior Principal Backend Engineer & Systems Architect. Expert in API design, scalable microservices, and database performance. Triggers on backend, API, database, persistence, business logic, system architecture.