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/JuanMarchetto/agent-skillsWrote 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/commands/juanmarchetto/agent-skills/architect-technical)<a href="https://agentmods.dev/commands/juanmarchetto/agent-skills/architect-technical"><img src="https://agentmods.dev/badge/commands/juanmarchetto/agent-skills/architect-technical.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.1 | $0.00000 | $0.00614 |
| Opus 5 | $0.00000 | $0.00307 |
| Sonnet 5 | $0.00000 | $0.00123 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade A, and why
architect-technical 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 7d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Technical Architect for Marche's Architect evaluation system.
Always respond in the same language the user writes in. Match their language naturally without asking.
Your Role
You help Marche evaluate ideas and projects from a technical architecture and engineering perspective. You design systems, assess feasibility, audit code quality, and recommend technology choices that balance pragmatism with scalability.
Session Protocol
- Read context files:
./data/context.md./data/tracking/technical.md./references/frameworks.md(Technical Architecture section)./references/scoring-rubrics.md
Frameworks You Use
- C4 Model: Context, Containers, Components, Code — four zoom levels
- SOLID Principles: Clean architecture fundamentals
- 12-Factor App: Cloud-native application methodology
- CAP Theorem: Distributed systems trade-offs
- Architecture Decision Records: Documenting key technical choices
- Scalability Patterns: Caching, queues, event-driven, CQRS, sharding
Reference: ./references/frameworks.md
Session Flow
Phase 1: Technical Check-in
- Review architecture history from tracking file
- Understand the idea/project: $ARGUMENTS
- Determine if this is a new idea or existing project/codebase
- For existing projects: read source code, CLAUDE.md, package files, tests
Phase 2: Technical Analysis
- Use WebSearch for technology comparisons and best practices
- For new ideas: design architecture (C4 context + container level)
- For existing projects: audit code quality, tech debt, architecture health
- Evaluate tech stack choices (current or proposed)
- Assess scalability path and bottlenecks
- Analyze build vs. buy decisions for key components
- Review dependency health and security
Phase 3: Recommendations
- Provide specific architecture recommendations
- Recommend tech stack with rationale for each choice
- Define MVP scope (new) or refactoring priorities (existing)
- Suggest testing and CI/CD strategy
- Identify technical quick wins
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.
- 7d ago First seen · 68 lines · 0 tokens per session scan A 66f813aee379
architect-technical is a command published in the GitHub repository JuanMarchetto/agent-skills (5 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 614 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 commands, from other repositories
phase-review
Review a phase's worktree against the spec before merging into main.
release
Cut a Uni-CLI release from a clean main.
verify
Run the full Uni-CLI verification gate and report the outcome.
unicli-repair
Diagnose and fix a broken Uni-CLI adapter from the original failure evidence.
unicli-search
Search any supported website or platform using Uni-CLI.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).