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 krzysztofsurdy/code-virtuoso --skill architectgit clone --depth 1 https://github.com/krzysztofsurdy/code-virtuosoWrote 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/krzysztofsurdy/code-virtuoso/architect)<a href="https://agentmods.dev/skills/krzysztofsurdy/code-virtuoso/architect"><img src="https://agentmods.dev/badge/skills/krzysztofsurdy/code-virtuoso/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.1 | $0.00068 | $0.01434 |
| Opus 5 | $0.00034 | $0.00717 |
| Sonnet 5 | $0.00014 | $0.00287 |
| Haiku 4.5 | $0.00007 | $0.00143 |
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 8d 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect
Own the technical design for a feature or system. Translate product requirements into component boundaries, data flows, API contracts, and technology choices that the development team builds against.
Role Summary
- Responsibility: Define how the system is structured — components, boundaries, contracts, and technology choices
- Authority: Make technology selections, define component boundaries, approve API contracts, set quality attribute targets
- Escalates to: Product Manager when requirements conflict with technical feasibility or require scope changes
- Deliverables: Architecture overview, API contracts, component specifications, ADRs
When to Use
- Designing a new system or significant feature from scratch
- Making technology choices that affect multiple components
- Defining API contracts between frontend and backend
- Evaluating trade-offs between quality attributes (performance vs maintainability, etc.)
- Reviewing an existing architecture for gaps or risks
Workflow
Phase 1: Analyze
Input: PRD, requirements, existing system context
- Review the PRD and identify all functional requirements that drive architecture
- Identify non-functional requirements — performance targets, scalability needs, security constraints
- Map existing system components that will be affected
- List technical constraints — existing tech stack, infrastructure limits, team expertise
- Identify risks and unknowns that need investigation
Output: Requirements analysis, constraints list, risk register
Phase 2: Design
Input: Requirements analysis, constraints
- Define component boundaries — what each component owns and doesn't own
- Design data flow between components — sequence diagrams or data flow descriptions
- Define API contracts — endpoints, request/response shapes, error codes
- Choose technologies where new choices are needed (with rationale)
- Design data models — entities, relationships, storage strategy
- Plan for cross-cutting concerns — authentication, logging, error handling, monitoring
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.
- 8d ago First seen · 156 lines · 68 tokens per session scan A fb22113a6e03
architect is a skill published in the GitHub repository krzysztofsurdy/code-virtuoso (21 stars, last pushed 3mo ago), licensed MIT. It adds 68 tokens to every session and 1,434 once invoked, about $0.0003 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 skills, from other repositories
hermes-diagnostic-review
Use when running a read-only diagnostic review of recent Hermes sessions to find recurring mistakes, failed tool calls, and repeated fixes, then propose suggestion-only improvements and reusable skills. Human-gated; never auto-applies.
instruction-eval
Change one condition an agent runs under (instruction text, the reference material instructions point at, MCP tools and permissions, hooks, skill files), then run the same prompts before and after, several times each, to see what actually changes. Produces an HTML report showing both arms' answers side by side. Use…
worth-building
Decide how elaborate to build something (simple vs. robust) and return a concrete, PoC-shaped proposal at that level — not over- or under-engineered, but right-sized. Use whenever someone is building something and the investment level is unclear: "quick or proper?", "MVP vs. real product", "is this over-engineering?"…
django-ticket-triage
Analyze a Django Trac ticket and produce a triage recommendation report — duplicate search, related PRs, forum threads, and the affected source code. Use when the user gives a Django ticket number, or asks whether a ticket is valid, a duplicate, or ready for a triage stage.
gh-issues
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5]…
healthcheck
Host security hardening and risk-tolerance configuration for OpenClaw deployments. Use when a user asks for security audits, firewall/SSH/update hardening, risk posture, exposure review, OpenClaw cron scheduling for periodic checks, or version status checks on a machine running OpenClaw (laptop, workstation, Pi, VPS).