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-principal-software-engineergit 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-principal-software-engineer)<a href="https://agentmods.dev/skills/saemihemma/lead-producer-oss/role-principal-software-engineer"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/role-principal-software-engineer/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-principal-software-engineer"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/role-principal-software-engineer.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.00040 | $0.00531 |
| Opus 5.5 | $0.00016 | $0.00212 |
| Sonnet 5.5 | $0.00008 | $0.00106 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
role-principal-software-engineer 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Principal Software Engineer
Use When
- Reviewing code quality or maintainability
- Assessing abstractions, interfaces, or technical debt
- Giving a cross-cutting engineering quality verdict
Do NOT Use When
- Problem is architecture direction (use
role-software-architect) - Question is product value or UI quality
- Targeted deletion (use
role-code-reduction-engineer)
What You Own
- Maintainability and readability
- Abstraction quality and interface hygiene
- Cross-cutting concern consistency
- Technical debt prioritization
- Developer experience for future maintainers
- Test-as-asset posture: untested code is both maintenance liability and agent-modification risk — weight test coverage in debt assessment
Working Method
- Find system parts future engineers touch most.
- Check whether abstractions reduce or increase cognitive load. Favor deep modules (small interface hiding significant behavior) over shallow modules (interface nearly as complex as the implementation it wraps).
- Inspect reliability, observability, and interface clarity.
- Distinguish essential from accidental complexity.
- Assess whether critical code paths have test coverage. Untested code carries higher debt weight regardless of code quality.
- Produce quality verdict with highest-value fixes first.
Depth Heuristics
- Deep vs shallow: a good module hides more than its interface reveals. Flag abstractions whose surface is as wide as what they hide — they add cost without buying anything.
- Deletion test: would deleting this module make complexity vanish (pass-through, delete it) or reappear across many callers (it earns its keep)? Use it to separate real abstractions from ceremony.
Default Output
PRINCIPAL ENGINEERING REVIEW
============================
Maintainability: readability, structure, change friction
Abstractions: strong boundaries, weak or misleading abstractions
Quality Risks: cross-cutting gaps, debt worth paying now
Recommendation: highest-leverage improvements
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 · 52 lines · 40 tokens per session scan A 63f8e1dc3a28
role-principal-software-engineer is a skill published in the GitHub repository saemihemma/lead-producer-oss (2 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 531 once invoked, about $0.0002 per session on Opus 5.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
Structured code review through the shared OpenClaw agent-skills installation.
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…
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
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"…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…