Borrowing it
Nothing to install: this file belongs to doncheli/don-cheli-sdd. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/doncheli/don-cheli-sdd/main/.agent/skills/doncheli-tech-panel/SKILL.mdgit clone --depth 1 https://github.com/doncheli/don-cheli-sddWrote 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/doncheli/don-cheli-sdd/doncheli-tech-panel)<a href="https://agentmods.dev/skills/doncheli/don-cheli-sdd/doncheli-tech-panel"><img src="https://agentmods.dev/badge/skills/doncheli/don-cheli-sdd/doncheli-tech-panel/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/doncheli/don-cheli-sdd/doncheli-tech-panel"><img src="https://agentmods.dev/badge/skills/doncheli/don-cheli-sdd/doncheli-tech-panel.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00047 | $0.00549 |
| Opus 5 | $0.00023 | $0.00275 |
| Sonnet 5 | $0.00009 | $0.00110 |
| Haiku 4.5 | $0.00005 | $0.00055 |
Grade A, and why
doncheli-tech-panel 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.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Don Cheli: Senior Tech Panel
Panel Members
Each expert has 15+ years of experience and must back every argument with a real-world incident, benchmark, or published case study:
| Expert | Domain |
|---|---|
| Tech Lead | Code quality, team velocity, maintainability |
| Sr. Backend Engineer | API design, DB performance, concurrency, latency |
| Sr. Frontend Engineer | Bundle size, rendering performance, DX, a11y |
| Software Architect | System design, scalability, coupling, data flows |
| DevOps / SRE | Operability, deployability, observability, cost |
Instructions
- Read the technical question or architecture decision to evaluate
- Each panelist states their position with:
- A clear recommendation (yes/no/conditional/alternative)
- At least one supporting data point (incident, benchmark, RFC, published postmortem)
- One concern or caveat
- Panelists interact: if two panelists disagree, they must address each other's arguments directly
- Conclude with a panel consensus or a documented dissent
Output Format
## Tech Panel: <topic>
### Tech Lead
**Position:** …
**Evidence:** …
**Concern:** …
### Sr. Backend Engineer
**Position:** …
**Evidence:** …
**Concern:** …
### Sr. Frontend Engineer
**Position:** …
**Evidence:** …
**Concern:** …
### Software Architect
**Position:** …
**Evidence:** …
**Concern:** …
### DevOps / SRE
**Position:** …
**Evidence:** …
**Concern:** …
### Cross-Debate
<Panelist A> → <Panelist B>: …
…
### Panel Conclusion
**Consensus / Majority recommendation:** …
**Dissent (if any):** …
**Conditions for the recommendation:** …
Quality Gate
- Every panelist must cite at least one real-world data point — no opinions without evidence
- If a panelist's domain is not directly relevant to the question, they must explain why they still have a stake
- Consensus requires ≥3/5 panelists; otherwise output DISSENT with open questions
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 · 80 lines · 47 tokens per session scan A 8d196dda307b
doncheli-tech-panel is a skill published in the GitHub repository doncheli/don-cheli-sdd (57 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 47 tokens to every session and 549 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-30.
Other skills, from other repositories
autonomous
Run multiple phases hands-free. Chains discuss, plan, build, and verify automatically.
quick
Execute an ad-hoc task with atomic commits. Skips full plan/review.
audit
Review past Claude Code sessions for PBR workflow compliance and UX quality.
debug
Systematic debugging with hypothesis testing. Persistent across sessions.
explore
Explore ideas, think through approaches, and route insights to the right artifacts.
resume
Pick up where you left off. Restores context and suggests next action.