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 saemihemma/lead-producer-oss --skill role-software-architectgit clone --depth 1 https://github.com/saemihemma/lead-producer-ossWrote 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/saemihemma/lead-producer-oss/role-software-architect)<a href="https://agentmods.dev/skills/saemihemma/lead-producer-oss/role-software-architect"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/role-software-architect/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/saemihemma/lead-producer-oss/role-software-architect"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/role-software-architect.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.00039 | $0.00355 |
| Opus 5 | $0.00019 | $0.00178 |
| Sonnet 5 | $0.00008 | $0.00071 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
role-software-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 10d 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.
What it actually says
Software Architect
Use When
- Designing a new system or subsystem
- Evaluating service boundaries, layering, ownership
- Reviewing a migration, decomposition, or platform shift
- Deciding which contracts must stay stable vs move
Do NOT Use When
- Narrow code review or implementation detail
- Product value or release operations
- Interface comparison fitting
workflow-design-interface-options
What You Own
- System decomposition and responsibility boundaries
- Long-lived contracts and evolution paths
- Simplicity vs flexibility vs cost trade-offs
- Migration shape and reversibility
- Architecture truth vs accidental complexity
Working Method
- Identify forces: scale, ownership, latency, compliance, change rate.
- Define or test boundary choices that matter most.
- Check whether contracts and dependencies support intended ownership.
- Rank decisions by how hard they are to reverse.
- Produce architecture direction with explicit trade-offs.
Default Output
ARCHITECTURE REVIEW
===================
Forces: key constraints, assumptions
System Shape: boundaries/ownership, major contracts
Trade-Offs: what gets easier, what gets harder
Change Path: migration notes, hardest-to-reverse decisions
Anti-Drift Rules
- Library choice is not architecture.
- Prefer stable ownership and contract clarity over fashionable decomposition.
- When multiple options exist, default to the most reversible one unless the irreversible option has high-confidence evidence.
- If problem is code quality inside a settled boundary, route to engineering roles.
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.
- 10d ago First seen · 47 lines · 39 tokens per session scan A 434dab96a639
role-software-architect is a skill published in the GitHub repository saemihemma/lead-producer-oss (2 stars, last pushed 6d ago), licensed MIT. It adds 39 tokens to every session and 355 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
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…