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/alternative)<a href="https://agentmods.dev/commands/ahmedhabiba/architor/alternative"><img src="https://agentmods.dev/badge/commands/ahmedhabiba/architor/alternative.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.00000 | $0.00484 |
| Opus 5 | $0.00000 | $0.00242 |
| Sonnet 5 | $0.00000 | $0.00097 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
alternative 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 8d 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.
Read .arch/state.json first.
GATE CHECK: Something must be in awaiting_acceptance status. If nothing is pending, say: "Nothing is currently pending. Use /status to check state."
The user wants a fundamentally different approach. Their request is in $ARGUMENTS.
If Phase 2 (Methodology):
- Propose a COMPLETELY different architecture pattern
- Don't just tweak the existing one — rethink from the requirements
- Compare the new proposal against the previous one explicitly
- Rewrite
.arch/phase2-methodology.mdand.arch/phase2-components-overview.md - Append to
.arch/decisions.md:### [DEC-NNN] Phase 2 | Alternative - **Decision:** Alternative methodology. New: [pattern] - **Rationale:** [user's reason for requesting alternative] - **Alternatives:** Previous approach: [previous pattern] - **Trade-offs:** [what changed — improvements and regressions] - **Risk:** [residual risk of the new approach] - **Supersedes:** [DEC-NNN of the previous proposal decision for this target] - **Date:** [timestamp]
If Phase 3 (Component):
- Redesign the current component around the alternative technology the user suggested
- Show how the alternative changes integration points with other components
- Compare: what improves, what gets worse, what stays the same
- Rewrite
.arch/components/[current_component].md - Append to
.arch/decisions.md:### [DEC-NNN] Phase 3 | Alternative - **Decision:** Alternative technology for [component]. New: [tech] - **Rationale:** [user's reason] - **Alternatives:** Previous: [previous tech] - **Trade-offs:** [what improves, what gets worse] - **Risk:** [residual risk] - **Supersedes:** [DEC-NNN of the previous proposal decision for this component] - **Date:** [timestamp]
After presenting the alternative:
- Status remains
awaiting_acceptance - Present comparison table: Original vs Alternative
- Ask: "Do you prefer this alternative, want to go back to the original, or refine further?"
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.
- 8d ago First seen · 47 lines · 0 tokens per session scan A a13c2186cc6e
alternative is a command published in the GitHub repository AhmedHabiba/architor (6 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 484 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.
Other commands, from other repositories
learn
Force claude-smart to extract learnings from this session now.
init
Install the formatters this repository needs, with every command visible before it runs.
brand-generate
Generate an on-brand document from a saved Brand Profile.
genshijin-compress
A command for safely shortening Markdown or text files into the genshijin style.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
audit-plugin
Audit plugin skills, commands, and agents for structure, size, and naming issues.