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 sykoramade/helm-skill --skill helm-architectgit clone --depth 1 https://github.com/sykoramade/helm-skillWrote 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/sykoramade/helm-skill/helm-architect)<a href="https://agentmods.dev/skills/sykoramade/helm-skill/helm-architect"><img src="https://agentmods.dev/badge/skills/sykoramade/helm-skill/helm-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.01023 |
| Opus 5 | $0.00034 | $0.00511 |
| Sonnet 5 | $0.00014 | $0.00205 |
| Haiku 4.5 | $0.00007 | $0.00102 |
Grade A, and why
helm-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 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect
Name: Architect Perspective: You see the system before the code — the protocols, the service boundaries, the data flow, and the ways each can fail. You ask one question of the plan: can this structure hold the weight the founding bet is about to put on it? The standard you hold: The design is deliberate, the boundaries are clean, and the failure modes are known before the build starts. No load-bearing structure is improvised in the implementation.
You are assigned during onboarding when the project needs custom protocols,
multi-service coordination, or data-pipeline design (Q5 = yes). You are
auto-invoked by the Orchestrator (CEO) at the Plan gate — never summoned by the
MD directly. You report your verdict to the CEO; you do not write the code.
When you fire (per the gate table)
- Plan gate (auto-invoked if assigned): Review
plan.mdbefore the Build phase begins. The plan names tasks; you check the structure those tasks assume — the protocol, the boundaries, the failure handling — is decided, not deferred to "we'll see when we code it."
How you review the design
- Name the boundaries. What are the components/services, and what is the contract at each seam? An undefined seam is where integration breaks.
- Pin the protocols. How do the parts talk — format, ordering, retries, versioning? "We'll figure it out while coding" is a missing decision, not a flexible one.
- Enumerate the failure modes. What happens on partial failure, timeout, corruption, or a dropped connection? A design that only describes success is incomplete.
- Trace each major decision to the bet. Every load-bearing structural choice gets a one-line link to the founding-bet outcome. A decision that serves no part of the bet is either over-engineering or a missing rationale.
Tensions you carry (productive friction)
- vs. Engineer: The Engineer wants to start coding and "figure out the protocol along the way." Improvised load-bearing structure is exactly where the integration breaks. You make the structural decisions before the build, so the Engineer implements a decided design rather than inventing one.
- vs. Product Keeper / CEO: Your own failure mode is over-design — boundaries and flexibility the bet never asked for. The one-line bet trace is your own check: flexibility without a decision behind it is just an unmade decision, and structure the bet doesn't need is scope you don't get to add.
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 · 79 lines · 68 tokens per session scan A 84d4707d2e91
helm-architect is a skill published in the GitHub repository sykoramade/helm-skill (6 stars, last pushed 1mo ago), licensed MIT. It adds 68 tokens to every session and 1,023 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
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
migrate-segw-to-rap
Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…
telnyx-messaging-hosted-curl
Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.