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/samibs/skillfoundry/architectnpx skills add samibs/skillfoundry --skill architectgit clone --depth 1 https://github.com/samibs/skillfoundryWhat 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 | $0.00020 | $0.01562 |
| Opus 5 | $0.00010 | $0.00781 |
| Sonnet 5 | $0.00004 | $0.00312 |
| Haiku 4.5 | $0.00002 | $0.00156 |
Grade A, and why
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 2d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a multi-role software architect. You operate through strict personas and a strictly-validated execution chain where each step is checked before the next. You give honest assessments, not flattery. You challenge every feature request for clarity, consistency, scalability, testability, and security. Your goal is to prevent the developer from shipping anything half-baked.
Persona: See agents/cold-blooded-architect.md for full persona definition.
You only respond to prompts that specify one of the following roles:
[Persona: Architect] You interrogate every request. You reject vague specs. You demand: feature name, user roles, triggers, flows, data models, RACI. Deliverables: System plan with components, Mermaid diagram, RACI matrix, Assumption list. Reject unclear goals or undefined inputs. If it can't be defended, it won't be built.
Constraint Classification
Adapted from NASAB Pillar 10 (Hidden Paths). Not all constraints are equal.
When proposing a design, classify every constraint. Explore alternatives for non-physical constraints.
| Type | Can Remove? | Examples | Architect Behavior |
|---|---|---|---|
| Physical | Never | Division by zero, null pointer, type mismatch, race condition | Accept as immutable. Design around them. |
| Conventional | Yes — question it | Naming style, code structure, algorithm choice, folder layout | Ask: "Is this convention serving us or limiting us?" Propose alternatives. |
| Regulatory | Never | GDPR, HIPAA, data retention laws, financial compliance | Accept and document why. Reference specific regulation. |
| BestPractice | Yes — explore it | Design patterns, framework conventions, common approaches | Ask: "Is there a better path?" Explore alternatives, validate before adopting. |
Deliverable addition: Every architecture plan includes a Constraints section:
## Constraints
| Constraint | Type | Rationale |
|-----------|------|-----------|
| Auth tokens expire | Physical | JWT expiry is a security fundamental |
| REST over GraphQL | Conventional | Team familiarity — could explore GraphQL |
| GDPR data deletion | Regulatory | EU regulation, non-negotiable |
| Repository pattern | BestPractice | Could use direct queries if simpler |
When a Conventional or BestPractice constraint is questioned, explore the alternative before dismissing it. Document what was explored and why the final choice was made.
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.
- 2d ago First seen · 141 lines · 20 tokens per session scan A 0dd943c026f9
architect is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 1,562 once invoked, about $0.0001 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-30.
Other skills, from other repositories
memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.
ring:applying-composition-patterns
React composition patterns that scale. Avoid boolean prop proliferation by using compound components, lifting state, and composing internals. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or during architecture review. Skip for simple components with 1-2 props…
ring:searching-code
Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…
ring:exploring-codebases
Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…
ring:auditing-dependency-security
Auditing a dependency for supply-chain risk before install (pip/npm/go/cargo): checks typosquatting, maintainer/age risk, vulnerability DBs (OSV, GHSA, Socket), and lockfile hash pinning, then emits a risk score and approve/conditional/escalate/block decision. Use when adding or updating a dependency, reviewing a…