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 AhmedHabiba/architor --skill architecture-methodologygit clone --depth 1 https://github.com/AhmedHabiba/architorWrote 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/ahmedhabiba/architor/architecture-methodology)<a href="https://agentmods.dev/skills/ahmedhabiba/architor/architecture-methodology"><img src="https://agentmods.dev/badge/skills/ahmedhabiba/architor/architecture-methodology/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ahmedhabiba/architor/architecture-methodology"><img src="https://agentmods.dev/badge/skills/ahmedhabiba/architor/architecture-methodology.svg" alt="Reviewed on agentmods" width="80" 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.00118 | $0.01315 |
| Opus 5 | $0.00059 | $0.00658 |
| Sonnet 5 | $0.00024 | $0.00263 |
| Haiku 4.5 | $0.00012 | $0.00131 |
Grade A, and why
architecture-methodology 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 11d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Methodology Orchestrator
When This Skill Activates
Any conversation about system architecture, technology choices, component design, PRD analysis, or solution design.
Phase Definitions
| Phase | Name | Purpose |
|---|---|---|
| 1 | Evaluation | Analyse PRDs, extract functional and non-functional requirements, identify constraints and risks. No technology or component decisions yet. |
| 2A | Pattern | Select the architecture pattern (e.g. event-driven, microservices, monolith) and justify the choice. |
| 2B | Component Map | Establish the high-level component boundaries and technology stack. |
| 2C | Cross-Cutting | Decide cross-cutting concerns (auth, observability, data consistency, security). These become constraints for all Phase 3 component designs. |
| 3 | Components | Design individual components sequentially. Each component must be explicitly accepted before the next begins. |
| 4 | Finalisation | Consolidate all accepted components into a solution document, validate against Phase 1 requirements, produce deliverables. |
State File: .arch/state.json
ALWAYS read this file before every architecture-related response. It tracks the current phase and the acceptance status of each component. NEVER rely on conversation memory for phase state.
Example structure:
{
"current_phase": "methodology",
"phases": {
"evaluation": { "status": "accepted" },
"methodology": {
"status": "in_progress",
"sub_phase": "cross_cutting",
"pattern_accepted": true,
"components_overview_accepted": true,
"cross_cutting_accepted": false
}
},
"components": {
"api-gateway": { "status": "accepted" },
"auth-service": { "status": "in_progress" },
"data-layer": { "status": "pending" }
},
"decision_count": 7,
"reopens": { "count": 0, "max": 2 }
}
A component is accepted only when the user types the explicit command /accept or the single word ACCEPT in uppercase. Paraphrases such as "looks good", "fine", or "approved" are NOT acceptance — respond by asking the user to confirm with /accept.
What ships with it
19 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.
- evals/instructions.json 12 KB
- evals/scenario-0/capability.txt 33 B
- evals/scenario-0/criteria.json 2.2 KB
- evals/scenario-0/task.md 2.7 KB
- evals/scenario-1/capability.txt 26 B
- evals/scenario-1/criteria.json 1.6 KB
- evals/scenario-1/task.md 1.4 KB
- evals/scenario-2/capability.txt 22 B
- evals/scenario-2/criteria.json 2.3 KB
- evals/scenario-2/task.md 2.1 KB
- evals/scenario-3/capability.txt 28 B
- evals/scenario-3/criteria.json 2.8 KB
- evals/scenario-3/task.md 3.4 KB
- evals/scenario-4/capability.txt 35 B
- evals/scenario-4/criteria.json 1.4 KB
- evals/scenario-4/task.md 2.7 KB
- evals/summary_infeasible.json 694 B
- evals/summary.json 1.3 KB
- tile.json 810 B
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.
- 11d ago First seen · 114 lines · 118 tokens per session scan A d946c79c44fb
architecture-methodology is a skill published in the GitHub repository AhmedHabiba/architor (6 stars, last pushed 6mo ago), licensed MIT. It adds 118 tokens to every session and 1,315 once invoked, about $0.0006 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
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
google-ads-audit
Google Ads account audit and business context setup. Use for account-health audits and business-context setup. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should I fix in my ads", or when the user is new to NotFair and hasn't run…
review
5-pass structured code review — correctness, security, performance, readability, consistency.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
extract-resume
Parse a resume's uploaded PDF into structured JSON (basics, experience, projects, skills, education) and save it to the editor.
ensure-pipelines-host
Ensures the tenant has a usable Power Platform Pipelines host environment before any pipeline operation runs. Detects host state via the same resolution order as the Power Apps UI (org-db setting → BAP env metadata → default-custom-host setting); if any existing host (Platform or Custom) is found, uses it. If no host…