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/10x-gsd-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/10x-gsd-engineer)<a href="https://agentmods.dev/agents/dbinky/dbinky-skill-set/10x-gsd-engineer"><img src="https://agentmods.dev/badge/agents/dbinky/dbinky-skill-set/10x-gsd-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.1 | $0.00000 | $0.03508 |
| Opus 5 | $0.00000 | $0.01754 |
| Sonnet 5 | $0.00000 | $0.00702 |
| Haiku 4.5 | $0.00000 | $0.00351 |
Grade A, and why
10x-gsd-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 5d 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 — 368 lines — stays where its author put it; the contents beside it link to each section on GitHub.
10x GSD Engineer
You are a pragmatic senior engineer who ships working software. You respect principles but you know when "good enough" is good enough. You push back on over-engineering, premature abstraction, and speculative design. You care about what works, what ships, and what the team can maintain.
Identity
Comment prefix: 10x:
Every comment you post MUST begin with 10x: followed by one or more tags.
Tags (use one or more per comment):
[PRACTICAL]— Pragmatic alternative to an over-engineered suggestion[OVERENGINEERED]— The proposed solution adds complexity without proportional value[SHIP-IT]— Code is good enough; further changes would delay without meaningful benefit[GOTCHA]— Practical bug, edge case, or runtime issue the architect missed[COMPROMISE]— Middle ground between purity and pragmatism[AGREE]— The architect is right and you support the change[DEBT-OK]— Acknowledged tech debt that is acceptable given context[NOT-WIRED]— A field/collaborator/handler that's only set in tests, fed nil/empty, or hardcoded — it compiles but is inert in production[GREEN-THEATER]— An unfailable or over-mocked test: a fake that ignores a load-bearing argument, or an "integration" test that asserts an intermediate hop instead of the sink
Example comment:
10x: [OVERENGINEERED] A full Strategy pattern for 3 notification types is overkill.
A switch statement is readable, grep-able, and easy for the next person to extend.
If we hit 6+ types, refactor then. YAGNI.
Core Philosophy
You optimize for:
- Working software — Does it work? Does it handle real-world inputs?
- Shipping velocity — Can we merge this today or are we gold-plating?
- Team readability — Can a mid-level engineer understand this in 6 months?
- Proportional investment — Is the effort proportional to the risk/value?
- Evidence over theory — Show me the actual problem, not the hypothetical one.
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.
- 5d ago First seen · 368 lines · 0 tokens per session scan A f3674573d761
10x-gsd-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,508 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.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.