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.
git 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/commands/ahmedhabiba/architor/propose-methodology)<a href="https://agentmods.dev/commands/ahmedhabiba/architor/propose-methodology"><img src="https://agentmods.dev/badge/commands/ahmedhabiba/architor/propose-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/commands/ahmedhabiba/architor/propose-methodology"><img src="https://agentmods.dev/badge/commands/ahmedhabiba/architor/propose-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.00000 | $0.01551 |
| Opus 5.5 | $0.00000 | $0.00620 |
| Sonnet 5.5 | $0.00000 | $0.00310 |
| Haiku 4.5 | $0.00000 | $0.00155 |
Grade A, and why
propose-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 2mo 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.
Read .arch/state.json first.
GATE CHECK:
- If
current_phaseisevaluationandphases.evaluation.acceptedis false, STOP: "Phase 1 (Evaluation) must be accepted first. Run /accept or use /status to check progress." - If
current_phaseis notevaluationandcurrent_phaseis notmethodology, STOP: "Cannot propose methodology. Current phase is [phase]."
Read .arch/phase1-evaluation.md for the accepted analysis.
Read .arch/org-context.md for organizational constraints.
Determine which sub-phase to execute
Check phases.methodology:
- If
pattern_acceptedis false: Execute Phase 2A below - If
pattern_acceptedis true ANDcomponents_overview_acceptedis false: Execute Phase 2B below - If
components_overview_acceptedis true ANDcross_cutting_acceptedis false: Execute Phase 2C below - If all three are accepted: STOP: "Phase 2 is complete. All sub-phases accepted. Run /design-component to begin Phase 3."
Phase 2A — Architecture Pattern Proposal
Propose an architecture pattern. Your proposal MUST include:
1. Recommended Pattern
Name the pattern (e.g., Event-Driven Microservices, Modular Monolith, Serverless-First, CQRS, Layered Monolith, Hybrid).
2. Why This Pattern — Specific to THIS Project
Don't give generic benefits. Map each benefit to a specific requirement from the PRD.
- "I recommend [pattern] because requirement FR-007 needs [X], and this pattern provides [Y]"
- Reference the team profile: "Given your team of [N] with [skills], this pattern's operational complexity is manageable because..."
3. What You Sacrifice
Every pattern has costs. Be explicit:
- What becomes harder?
- What technical debt does this introduce?
- What future flexibility do you lose?
4. Alternatives Considered
Present at least 2 alternative patterns with brief comparison.
| Criterion | Recommended | Alternative 1 | Alternative 2 |
|---|---|---|---|
| Fits requirements | ... | ... | ... |
| Team capability | ... | ... | ... |
| Operational cost | ... | ... | ... |
| Time to deliver | ... | ... | ... |
| Future flexibility | ... | ... | ... |
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.
- 2mo ago First seen · 156 lines · 0 tokens per session scan A 489f04ca51e6
propose-methodology is a command published in the GitHub repository AhmedHabiba/architor (6 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,551 tokens. 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.
propose-methodology compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| propose-methodologyAhmedHabiba/architor | Command | 6 | 7mo ago | MIT | A | 0 | Claude Code |
| learnReflexioAI/claude-smart | Command | 791 | 4d ago | Apache-2.0 | A | 14 | Claude Code |
| prototypegrainulation/grainulator | Command | 86 | yesterday | MIT | A | 0 | Claude Code |
| initazrtydxb/procoder | Command | 211 | 11d ago | Apache-2.0 | A | 16 | Claude Code |
| genshijin-compressInterfaceX-co-jp/genshijin | Command | 331 | 27d ago | MIT | A | 17 | Claude Code |
| responsive-design-specialistimsaif/design-with-claude | Command | 11 | 2d ago | MIT | A | 36 | Claude Code |
| brand-generateferdinandobons/brand-docs | Command | 291 | 4mo ago | MIT | A | 0 | Claude Code |