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/scolladon/craft/architecturenpx skills add scolladon/craft --skill architecturegit clone --depth 1 https://github.com/scolladon/craftWrote 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/scolladon/craft/architecture)<a href="https://agentmods.dev/skills/scolladon/craft/architecture"><img src="https://agentmods.dev/badge/skills/scolladon/craft/architecture.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.00037 | $0.00638 |
| Opus 5 | $0.00018 | $0.00319 |
| Sonnet 5 | $0.00007 | $0.00128 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade A, and why
architecture 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 5d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
craft:architecture
Preamble (always runs — non-overridable)
-
Manifest read (lint if standalone). Standalone: scope = current branch vs default branch.
-
Resolve the active technique set from
phase.harness(the resolved descriptor), using the same ADR-149 discovery precedence — default-off favours no-op:- Declared —
phase.harness.techniquePlan(engine-emitted) wins outright: each entry specifies techniqueid,runcommand,mode(gate|triage), optionalscope, optionaltriage-procedureref.run-styledefaults tosync. - Derived — absent a declaration, read the repo's own boundary-check conventions (README / CONTRIBUTING / craft config) and derive one technique per documented dependency/import-boundary validation command, each GATE or TRIAGE per its nature.
- No-op (terminal) — absent any declared or derived technique: record
NO-OP(architecture): no techniques declared/probedand release thepropose-gate entry; the phase ends here. This phase is default-off; no-op is the expected outcome in most repos.
Every resolved technique command — declared or derived — is trusted operator input (same trust model as the manifest and
context:files); the derived tier reads the repo's own committed conventions, never an untrusted external source.For each resolved technique, run its
probe(config-file presence / binary resolvable). A failed probe declines the technique by absence:NO-OP(architecture:<technique-id>): declined — probe absent. When every technique is declined: the phase ends here. - Declared —
Procedure (default body — a manifest override: replaces everything below)
- Per-active-technique walk (
run-style: syncdefault — no lock against teardown). For each technique in the resolved active set, scope per the technique'sscope(default: the change's touched code, never wider). Capture the violation/finding report. - The PR waits for triage (orchestrator invariant): on a non-empty finding set,
spawn craft:harness-triager with: the findings; the gate; the commit message
fix(architecture): <technique-id> <scope>(orchore(architecture): <technique-id> <scope>for an exception-only landing); global + architecture-phasecontext:files verbatim; the technique'striage-procedureref (if declared). - Verify the triager's commit; run the phase gate; record per-finding outcomes in the run record.
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.
- 5d ago First seen · 47 lines · 37 tokens per session scan A 93c6d1c22c47
architecture is a skill published in the GitHub repository scolladon/craft (2 stars, last pushed 17d ago), licensed MIT. It adds 37 tokens to every session and 638 once invoked, about $0.0002 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
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
define
Manifest builder. Turns shared understanding into a verifiable Manifest with Deliverables, Acceptance Criteria, Global Invariants, and an Initial Approach. Use when planning features, scoping refactors, debugging complex issues, or when the user asks to define, scope, plan, spec out, make a manifest, or break down a…
vertical-real-estate
Residential-proptech domain knowledge so architect / pm aren't naive when speccing real-estate products (listings, lead-crm, transaction-coordination, property-mgmt). Codifies MLS/IDX reality, listing status lifecycle + syndication canonical-source, long-cycle lead nurture, transaction-coordination as the high-pain…
skeptical-triage
Reusable 3-round self-challenge + arbiter pattern for filtering false positives from findings/verdicts. Use when the cost of a false-positive gate block exceeds the cost of 4 extra LLM turns.
anti-patterns
Catalogue of known SDLC anti-patterns that greatcto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
cost-model
Standardized cost-estimation framework for greatcto plans. Forces explicit LLM cost, infra cost, human-supervision time, and the (defensible) human-equivalent comparison. Output format is parsable by the board's /api/cost path — must follow exactly.