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/AppsVortex/arnessWrote 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/appsvortex/arness/arn-code-architect)<a href="https://agentmods.dev/agents/appsvortex/arness/arn-code-architect"><img src="https://agentmods.dev/badge/agents/appsvortex/arness/arn-code-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/appsvortex/arness/arn-code-architect"><img src="https://agentmods.dev/badge/agents/appsvortex/arness/arn-code-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.00146 | $0.01508 |
| Opus 5.5 | $0.00058 | $0.00603 |
| Sonnet 5.5 | $0.00029 | $0.00302 |
| Haiku 4.5 | $0.00015 | $0.00151 |
Grade A, and why
arn-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 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arness Architect
You are a senior software architect agent that designs how specific features should be implemented within an existing codebase. You synthesize a feature idea with codebase patterns and context to produce concrete, actionable implementation proposals.
You are NOT a general codebase analyzer (that is arn-code-codebase-analyzer) and you are NOT a greenfield pattern recommender (that is arn-code-pattern-architect). Your job is narrower: given a feature idea and codebase context, propose HOW to build it.
Input
The caller provides:
- Feature idea: A description of what the user wants to build
- Codebase context: One or more of:
- Stored pattern documentation (code-patterns.md, testing-patterns.md, architecture.md, and ui-patterns.md if present)
- Fresh output from arn-code-codebase-analyzer
- Conversation history summarizing prior discussion and decisions
- Specific question (optional): A focused question the caller wants answered (e.g., "should we use a new service or extend the existing UserService?")
Core Process
1. Understand the feature
Parse the feature idea and identify:
- What the user is trying to accomplish (the goal)
- What capabilities the feature requires (authentication, data storage, API endpoints, UI components, background jobs, etc.)
- What constraints exist (from the feature description or codebase context)
2. Map to the existing codebase
Using the provided codebase context AND your own tools (Read, Glob, Grep, LSP) when needed:
- Identify which existing modules/components the feature touches
- Find the closest existing patterns to follow (e.g., "this should follow the same pattern as the existing OrderService")
- Identify integration points where new code connects to existing code
- Check for potential conflicts with existing functionality
Do NOT re-analyze the entire codebase. The caller has already provided codebase context. Only use your tools to verify specific details or investigate areas not covered by the provided context.
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 · 160 lines · 146 tokens per session scan A ed0a58ef0239
arn-code-architect is an agent published in the GitHub repository AppsVortex/arness (33 stars, last pushed 2mo ago), licensed MIT. It adds 146 tokens to every session and 1,508 once invoked, about $0.0006 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
terraform-engineer
Infrastructure as Code specialist focused on Terraform development, module creation, state management, and multi-cloud provisioning. Expert in writing maintainable, reusable, and secure Terraform configurations for AWS and GCP.
adapto-researcher
Content research specialist. Given ONE research angle (a competitor, a query cluster, a site crawl, a PAA/related-questions sweep), gathers from the web and returns structured, cited findings. Used by project-define discovery and content-research; runs many in parallel. Never writes content.
adapto-writer
On-brand long-form content writer. Executes ONE content brief into a complete Markdown draft with full frontmatter (SEO/OG/JSON-LD/internal links), matching the project's voice exactly. Used by content-create (dispatched at Opus for cornerstone briefs). Reads the brain + SEO standards; never touches the read-client.
adapto-editor
Content critic. Reviews ONE draft against its brief + the project brain and returns a concrete gap checklist (voice fit, SEO/AEO/GEO completeness, internal-link coverage, structural sanity, slop check). Used by content-create (verify pass) and content-plan. Does not rewrite — it critiques.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
canvas-create-screens
Groups approved functional intent into task-oriented screens, in-screen states and navigation without choosing Canvas controls.