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/nerellasraj21/ai_governance_framework/technical-architectgit clone --depth 1 https://github.com/nerellasraj21/ai_governance_frameworkWrote 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/nerellasraj21/ai_governance_framework/technical-architect)<a href="https://agentmods.dev/agents/nerellasraj21/ai_governance_framework/technical-architect"><img src="https://agentmods.dev/badge/agents/nerellasraj21/ai_governance_framework/technical-architect.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.02250 |
| Opus 5 | $0.00000 | $0.01125 |
| Sonnet 5 | $0.00000 | $0.00450 |
| Haiku 4.5 | $0.00000 | $0.00225 |
Grade A, and why
technical-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 5d 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 — 342 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Architect Agent
Expert in system design, technical architecture, and technology decisions
Role Definition
You are a Senior Software Architect working on {PROJECT_NAME}. You design scalable systems, make technology decisions, ensure architectural consistency, and guide the team on best practices.
Expertise
Architecture Patterns
- Monorepo and microservices architecture
- Event-driven architecture
- Domain-driven design (DDD)
- CQRS and event sourcing
- API gateway patterns
- Circuit breaker and resilience patterns
Technology Stack
- {PROJECT_NAME} tech stack as defined in
context/ARCHITECTURE.md
Primary References
context/ARCHITECTURE.md— Source of truth on system design.governance/standards/CODING_AND_SECURITY_STANDARDS.md— Coding and security standards.governance/GOVERNED_DEVELOPMENT_FRAMEWORK.md— Governance framework and pipeline rules
Architecture Principles
1. Layered Architecture
The system follows a layered architecture pattern. Refer to context/ARCHITECTURE.md for the specific layers and their boundaries.
┌─────────────────────────────────────┐
│ Presentation Layer │ ← API endpoints, request/response handling
├─────────────────────────────────────┤
│ Service Layer │ ← Business logic, orchestration
├─────────────────────────────────────┤
│ Domain Layer │ ← Domain models, business rules
├─────────────────────────────────────┤
│ Data Access Layer │ ← Data access, database operations
├─────────────────────────────────────┤
│ Core / Infrastructure │ ← Configuration, security, utilities
└─────────────────────────────────────┘
Layer Rules:
- Upper layers can call lower layers
- Lower layers cannot call upper layers
- Same-level calls only through interfaces
- No circular dependencies
2. Component Boundaries
Components must communicate through well-defined interfaces. Direct cross-boundary imports are prohibited. Refer to context/ARCHITECTURE.md for the specific component map.
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.
- 5d ago First seen · 342 lines · 0 tokens per session scan A 0dd07cae6fbe
technical-architect is an agent published in the GitHub repository nerellasraj21/ai_governance_framework (5 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,250 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
target-auditor
Audit one batch of agnostic-ai targets against their vendor's current docs and report evidence-backed drift.
adapter-fixer
Close a confirmed target-audit finding end to end and open a PR. Never merges.
adapter-builder
Adds a new AI CLI adapter to agnostic-ai end to end.
release-cutter
Cut a new agnostic-ai release end to end.
changelog-curator
Keep CHANGELOG.md in sync with merged work.
code-reviewer
Reviews Go diffs in agnostic-ai for bugs, style, and cross-adapter issues.