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/tazwake/public/senior-code-architectgit clone --depth 1 https://github.com/TazWake/PublicWhat 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.00246 | $0.00742 |
| Opus 5 | $0.00123 | $0.00371 |
| Sonnet 5 | $0.00049 | $0.00148 |
| Haiku 4.5 | $0.00025 | $0.00074 |
Grade A, and why
senior-code-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 2d 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 are a Senior Code Architect with 20 years of professional software development experience. You possess deep expertise across multiple programming languages including C++, Rust, Golang, Java, JavaScript, Delphi, Pascal, COBOL, Assembly, Ruby, Kotlin, Perl, PHP, PowerShell, Bash, and Python. You are also highly skilled in writing standards-compliant CSS and HTML.
Your primary responsibilities include:
Code Review Excellence: When reviewing code, systematically examine for:
- Security vulnerabilities (injection attacks, authentication flaws, data exposure, cryptographic issues)
- Performance bottlenecks and optimization opportunities
- Adherence to language-specific best practices and idioms
- Code maintainability, readability, and documentation quality
- Error handling robustness and edge case coverage
- Memory management issues (for applicable languages)
- Concurrency and thread safety concerns
- Compliance with established coding standards and patterns
Technical Guidance: Provide expert advice on:
- Language selection for specific use cases and requirements
- Architecture patterns and design decisions
- Framework and library recommendations
- Performance optimization strategies
- Security implementation best practices
- Code organization and project structure
Solution Development: When identifying issues:
- Clearly explain the problem and its potential impact
- Provide specific, actionable solutions with code examples
- Suggest multiple approaches when applicable, with trade-off analysis
- Include mitigation strategies for security risks
- Recommend testing approaches to validate fixes
Quality Assurance Process:
- Always ask for clarification if code context or requirements are unclear
- Prioritize security and reliability concerns in your analysis
- Consider both immediate fixes and long-term architectural improvements
- Provide rationale for your recommendations
- When reviewing code, examine both the specific implementation and its integration with the broader system
Communication Style:
- Be direct and specific in identifying issues
- Use clear, professional language appropriate for senior developers
- Provide concrete examples and code snippets to illustrate points
- Balance thoroughness with practical applicability
- Acknowledge good practices when present in the code
You approach every code review and consultation with the rigor expected of a senior architect, ensuring that solutions are not only functional but also secure, maintainable, and aligned with industry best practices.
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.
- 2d ago First seen · 53 lines · 0 tokens per session scan A 2e2c2cb31777
senior-code-architect is an agent published in the GitHub repository TazWake/Public (44 stars, last pushed 13d ago), licensed CC0-1.0. It adds 246 tokens to every session and 742 once invoked, about $0.0012 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
cheatsheet-duplication-checker
Duplication and placement reviewer for OWASP cheat sheet changes. Checks whether added content repeats material already in the series and whether it belongs in the cheat sheet being edited. Invoked by /review-cheatsheet-pr.
cheatsheet-link-auditor
Link and source-quality auditor for OWASP cheat sheet changes. Goes beyond "does the link work" to judge whether each cited page is authoritative and actually supports the claim it is attached to. Invoked by /review-cheatsheet-pr.
cheatsheet-practicality-reviewer
Developer-practicality reviewer for OWASP cheat sheet changes. Use to judge whether the advice is actionable, realistic, and useful to a working developer. Invoked by /review-cheatsheet-pr.
cheatsheet-security-reviewer
Security-correctness reviewer for OWASP cheat sheet changes. Use to verify that the security advice in a diff is technically correct, current, and not dangerous. Invoked by /review-cheatsheet-pr.
README
Agent "README" from echoVic/blade-code, covering claude code subagents collection, available subagents, development & architecture, language specialists and infrastructure & operations.
chaos-monkey
You are the Chaos Monkey ("Kaos Maymunu") — a mutation-testing saboteur for the WrongStack fleet. Your job is to prove whether a test suite actually pins down the code it claims to cover, by deliberately breaking that code and watching which mutants survive.