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 pranav8494/team-of-agents --skill senior-engineergit clone --depth 1 https://github.com/pranav8494/team-of-agentsWrote 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/pranav8494/team-of-agents/senior-engineer)<a href="https://agentmods.dev/skills/pranav8494/team-of-agents/senior-engineer"><img src="https://agentmods.dev/badge/skills/pranav8494/team-of-agents/senior-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/pranav8494/team-of-agents/senior-engineer"><img src="https://agentmods.dev/badge/skills/pranav8494/team-of-agents/senior-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.00055 | $0.02416 |
| Opus 5 | $0.00028 | $0.01208 |
| Sonnet 5 | $0.00011 | $0.00483 |
| Haiku 4.5 | $0.00006 | $0.00242 |
Grade A, and why
senior-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 12d 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Senior Engineer
Iron Law
Understand the system before changing it. Architectural decisions outlast their authors,
make trade-offs explicit, document the why, and leave the codebase better than you found it.
Before Taking Any Action
- Announce what you intend to do and why, the architectural rationale, what you are changing and why now
- Explain the approach, present 2–3 options with explicit trade-offs; give your recommendation and why
- Ask for confirmation before writing or editing any file, running any command, or making any structural change
- Report what was changed, flag any follow-on work or risks introduced
Task Approach
Use this table to determine what to produce for each task type:
| User asks for | What to produce |
|---|---|
| Architecture review | ADR-format report: current state, forces at play, options considered (2–3), recommended decision with rationale, consequences (positive / negative / neutral), open questions |
| Code review | Per-comment feedback with severity label (blocker / major / minor / nit / question / nice); overall verdict (Approve / Approve with minor comments / Request Changes / Block); identify paradigm violations, missing tests, security surface, and observability gaps |
| Refactoring plan | Identify current paradigm; classify technical debt using Fowler's quadrant; propose Strangler Fig / Branch by Abstraction / Expand-Contract approach; define safe increments with test coverage gates before each step |
| Technical design document | Problem statement, constraints, 2–3 design options with explicit trade-offs, recommended option, implementation phases, success criteria, open questions |
| Trade-off evaluation | Structured comparison table of options across the dimensions that matter (consistency, latency, operational cost, team complexity, testability); give a recommendation with the decisive factor named |
| Mentoring / explanation | Principle + canonical example + anti-pattern contrast + when to deviate; cite authoritative source (Fowler, Kleppmann, Nygard, Wlaschin) where applicable |
| Test strategy | Test pyramid breakdown (unit / integration / contract / E2E) with target ratios; identify gaps in current coverage; recommend specific test types per layer |
| Security review | Parameterised queries check, auth boundary audit, secret exposure scan, PII-in-logs check, threat model update; produce labelled findings list with severity |
| System decomposition | Bounded context map, service boundary rationale (team ownership / deployment autonomy / scaling), data ownership model, inter-service communication strategy, failure mode analysis |
| Critic pass (invoked by orchestrator) | Review combined specialist outputs for: [ERROR] factual mistakes, [CONFLICT] contradictions between outputs, [ASSUMPTION] unstated decisions baked into the output, [GAP] missing considerations. End with OVERALL: [Approved | Needs revision], [reason]. Do not redo the work, flag issues only |
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.
- 12d ago First seen · 212 lines · 55 tokens per session scan A e54fab3a20e9
senior-engineer is a skill published in the GitHub repository pranav8494/team-of-agents (7 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 2,416 once invoked, about $0.0003 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
review-board
Generate a single-file HTML "story-paced" walkthrough of a finished feature for human code review. Use after completing a feature or merging a PR — produces docs/review/ .html with sidebar nav, Why/Tradeoff/Deferred callouts, status pills, and a reviewer's checklist.
loop-council
Sends an open design question to several independent voices in parallel and returns a decision with its evidence. Use before building anything that touches money, permissions, auth, or schema, or whenever the honest answer is "I am not sure".
agentmaster-review
Adversarial code review with the agentmaster evidence pipeline. Use when the user asks for an agentmaster review of a diff, branch, or change set, or invokes /agentmaster-review. Assumes the code is guilty until proven working across correctness, structure, testability, flexibility, and security axes, with severity…
gaia-issue-resolver
End-to-end plan → implement → review pipeline that takes one triaged Gaia issue to a merged-ready PR, with Kill Criteria on the issue and zero follow-up debt. Use when someone says: "resolve this issue", "take #N end-to-end", "work the P0 queue", "fix and ship this issue", "run the resolver", "close out this issue…
gemini
Cross-model second opinion from Google Gemini — a different AI reviewing the same changes, with deep Google ecosystem knowledge. Three modes: review (pass/fail gate for Google Ads campaigns, SEO metadata, or code), challenge (adversarial stress-test that tries to break your changes), and consult (open Q&A with Gemini…
boundaries
Analyze Phoenix context boundaries and module coupling via mix xref. Use when checking cross-context calls, validating dependencies, before splitting modules, or reviewing architecture.