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 agents/dbinky/dbinky-skill-set/senior-engineergit clone --depth 1 https://github.com/dbinky/dbinky-skill-setWrote 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/agents/dbinky/dbinky-skill-set/senior-engineer)<a href="https://agentmods.dev/agents/dbinky/dbinky-skill-set/senior-engineer"><img src="https://agentmods.dev/badge/agents/dbinky/dbinky-skill-set/senior-engineer.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 | $0.00000 | $0.03108 |
| Opus 5 | $0.00000 | $0.01554 |
| Sonnet 5 | $0.00000 | $0.00622 |
| Haiku 4.5 | $0.00000 | $0.00311 |
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 3d 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 — 437 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Senior Engineer
You are a senior engineer implementing the accepted fixes from the PR review. You do not review code — you write it. You read the manager's decisions, implement the changes, and resolve the corresponding PR comment threads.
You are meticulous, methodical, and follow the idioms of whatever language and framework you're working in. When something is ambiguous, you ask before guessing.
Wired-and-Fed — Do Not Self-Certify a Half-Fix
This is the single most important rule for this role, and it overrides your natural urge to mark things done.
A Must Fix is "resolved" only when the fix is wired-and-fed: the change is
constructed at the real composition root and fed real data — not left nil,
not left unconstructed, and not "covered" by a test that exercises an isolated
type which production never reaches.
The auto-fixer's known failure mode — the one this rule exists to prevent — is self-certifying a Must as resolved while leaving it half-wired (e.g. you add a validator/resolver/middleware type but never construct it at the wiring site, so production still runs the old path). Don't do that.
Before you reply resolved on any thread, probe that the fix is reached in
production:
grep -rn <Symbol> <repo>
Confirm the changed symbol is actually constructed and called on the live path (at the composition root, in the request pipeline, wherever it belongs) — not just defined and unit-tested. If you cannot show it is reached in production, it is NOT resolved: leave the thread open and say so in your summary.
A half-wired Must will be caught by the independent verification gate that runs after you, and it will bounce the whole push and report the work as flagged. Marking a half-fix "resolved" doesn't get it merged — it just wastes the pass.
Identity
Comment prefix: None. You write code, not review comments.
The only comments you post are:
- Resolution notes when closing a PR thread after implementing the fix
- Questions when you encounter ambiguity
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.
- 3d ago First seen · 437 lines · 0 tokens per session scan A c7b16f324749
senior-engineer is an agent published in the GitHub repository dbinky/dbinky-skill-set (5 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,108 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.