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 skills add joaquimscosta/arkhe-claude-plugins --skill architectgit clone --depth 1 https://github.com/joaquimscosta/arkhe-claude-pluginsWrote 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/skills/joaquimscosta/arkhe-claude-plugins/architect)<a href="https://agentmods.dev/skills/joaquimscosta/arkhe-claude-plugins/architect"><img src="https://agentmods.dev/badge/skills/joaquimscosta/arkhe-claude-plugins/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/skills/joaquimscosta/arkhe-claude-plugins/architect"><img src="https://agentmods.dev/badge/skills/joaquimscosta/arkhe-claude-plugins/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.00082 | $0.01009 |
| Opus 5.5 | $0.00033 | $0.00404 |
| Sonnet 5.5 | $0.00016 | $0.00202 |
| Haiku 4.5 | $0.00008 | $0.00101 |
Grade A, and why
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 yesterday.
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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
System Architect
Analyze system architecture, module boundaries, API contracts, data models, and code patterns.
Context Discovery
Run the shared context discovery protocol in CONTEXT_DISCOVERY.md. Execute all phases in order (use deep scan mode for Phase 7). Also glob for architecture-specific documents:
docs/adr/**/*.md, docs/architecture/**/*.md, docs/design/**/*.md
After standard discovery, perform architecture-specific scans from TECH_STACK_DETECTION.md § Architecture-Specific Scanning (framework detection, architecture patterns, database patterns).
Arguments
Parse from $ARGUMENTS:
| Mode | Description |
|---|---|
module <name> |
Deep module structure analysis |
api <feature> |
API endpoint analysis and design guidance |
data-model <feature> |
Database schema and data model analysis |
boundaries |
Module boundary and coupling analysis |
patterns |
Pattern conformance check |
decisions |
ADR and decision traceability |
frontend <feature> |
Frontend architecture guidance |
| (none) | Ask what the user needs architectural guidance on |
Mode Execution
| Mode | Produces |
|---|---|
module <name> |
Structure, domain model, API surface, dependencies, maturity, quality assessment, and prioritized recommendations |
api <feature> |
Endpoint design (method, path, DTOs, auth, pagination, errors) matching existing patterns |
data-model <feature> |
Schema design (tables, types, relationships, indexes, migrations) matching existing models |
boundaries |
Import graph, shared references, coupling analysis, boundary violations |
patterns |
Pattern catalog with codebase examples (layering, DTOs, events, testing) |
decisions |
Decision traceability table (decision, evidence, status) |
frontend <feature> |
Component hierarchy, data flow, state management, design system integration |
See WORKFLOW.md for detailed execution steps per mode.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 99 lines · 82 tokens per session scan A e68186f15b87
architect is a skill published in the GitHub repository joaquimscosta/arkhe-claude-plugins (21 stars, last pushed yesterday), licensed MIT. It adds 82 tokens to every session and 1,009 once invoked, about $0.0003 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-10-16.
Other skills, from other repositories
gws-schema
Introspect any Google Workspace API schema — discover method parameters, request bodies, and response types before executing.
recipe-schema-explore
Discover and introspect any Google Workspace API before using it — explore methods, parameters, and types.
mcp-builder
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
rust-network-module
Add Rust async networking modules with project-adapted listener lifecycle, protocol parsing, and meaningful tests. Includes Tokio TCP and example wire-protocol templates for nat464-sidecar or compatible Rust projects.
gws-shared
Shared gws CLI setup, schema discovery, shell quoting, pagination, and authorization conventions for Google Workspace operations.
backend
Servers, routes, APIs, and backend architecture. Activated when Claude creates server-side code, API routes, or Express/Fastify/Next.js API handlers.