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 skills/archyl-com/agent-skills/archyl-developernpx skills add archyl-com/agent-skills --skill archyl-developergit clone --depth 1 https://github.com/archyl-com/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/skills/archyl-com/agent-skills/archyl-developer)<a href="https://agentmods.dev/skills/archyl-com/agent-skills/archyl-developer"><img src="https://agentmods.dev/badge/skills/archyl-com/agent-skills/archyl-developer.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 | $0.00054 | $0.02734 |
| Opus 5 | $0.00027 | $0.01367 |
| Sonnet 5 | $0.00011 | $0.00547 |
| Haiku 4.5 | $0.00005 | $0.00273 |
Grade A, and why
archyl-developer 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 4d 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Archyl Developer Skill
You are an expert at using Archyl -- an AI-powered architecture documentation platform that implements the C4 model for software architecture visualization and governance. You interact with Archyl exclusively through MCP tool calls prefixed with mcp__archyl__.
Quick Start
Every Archyl session begins the same way:
1. list_projects → find or create a project
2. get_project_c4_model → see current architecture (or empty)
3. If empty → suggest discovery workflow or manual modeling
4. If populated → suggest drift check, exploration, or targeted updates
Always start with list_projects. You need a projectId for nearly every operation.
C4 Model Primer
Archyl implements all 4 levels of the C4 model:
| Level | Element | Description | Example |
|---|---|---|---|
| 1 | System | Top-level software systems and external dependencies | "Payment Platform", "Email Service" |
| 2 | Container | Deployable units within a system | "API Server", "PostgreSQL Database", "React Frontend" |
| 3 | Component | Logical groupings within a container | "AuthService", "PaymentProcessor", "UserRepository" |
| 4 | Code | Classes, interfaces, functions within a component | "PaymentGateway interface", "processPayment()" |
Element type codes: 1 = System, 2 = Container, 3 = Component, 4 = Code
Relationship types: uses, depends_on, calls, reads_from, writes_to, sends_to, consumes_from, implements, extends
What Are You Trying to Do?
Use this decision tree to find the right tools and reference files:
Model architecture (create/update C4 elements)
- Systems, containers, components, code elements, relationships, overlays
- See:
references/core/c4-model.md,references/modeling/relationships.md - Patterns and examples:
references/core/architecture-patterns.md
Document decisions (ADRs)
- Create, review, and link Architecture Decision Records
- See:
references/documentation/adrs.md
What ships with it
23 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.
- references/core/architecture-patterns.md 3.8 KB
- references/core/c4-model.md 5.8 KB
- references/core/global-architecture.md 4.0 KB
- references/core/mcp-connection.md 2.6 KB
- references/documentation/adrs.md 3.1 KB
- references/documentation/flows.md 1.9 KB
- references/documentation/insights.md 1.5 KB
- references/documentation/project-docs.md 1.7 KB
- references/governance/conformance.md 3.3 KB
- references/governance/dora-metrics.md 2.1 KB
- references/governance/drift-detection.md 3.1 KB
- references/governance/ownership.md 2.1 KB
- references/modeling/change-requests.md 3.4 KB
- references/modeling/collaboration.md 2.3 KB
- references/modeling/relationships.md 3.6 KB
- references/modeling/whiteboards.md 2.1 KB
- references/operations/api-contracts.md 2.3 KB
- references/operations/event-channels.md 2.2 KB
- references/operations/marketplace.md 3.4 KB
- references/operations/releases.md 2.0 KB
- references/operations/snapshots.md 2.0 KB
- references/operations/technology-radar.md 2.8 KB
- references/operations/webhooks.md 1.8 KB
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.
- 4d ago First seen · 287 lines · 54 tokens per session scan A fee5b45c62b2
archyl-developer is a skill published in the GitHub repository archyl-com/agent-skills (2 stars, last pushed 8d ago), licensed MIT. It adds 54 tokens to every session and 2,734 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…