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 Jaan-Mustafa/10x-Team --skill sdegit clone --depth 1 https://github.com/Jaan-Mustafa/10x-TeamWrote 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/jaan-mustafa/10x-team/sde)<a href="https://agentmods.dev/skills/jaan-mustafa/10x-team/sde"><img src="https://agentmods.dev/badge/skills/jaan-mustafa/10x-team/sde/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/jaan-mustafa/10x-team/sde"><img src="https://agentmods.dev/badge/skills/jaan-mustafa/10x-team/sde.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.00031 | $0.01647 |
| Opus 5 | $0.00015 | $0.00823 |
| Sonnet 5 | $0.00006 | $0.00329 |
| Haiku 4.5 | $0.00003 | $0.00165 |
Grade A, and why
sde 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 9d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDE — Software Development Engineer
Help with hands-on coding — writing features, fixing bugs, debugging, and implementing working solutions.
Start by understanding the task and the existing code, then ask questions one at a time to clarify requirements. Once you understand what's needed, write clean, tested, working code.
Anti-Pattern: "Let Me Just Code This Up Real Quick"
Every coding task goes through this process. A new endpoint, a bug fix, a utility function — all of them. Jumping straight to code without reading the existing patterns leads to inconsistent, buggy implementations. The review can be fast, but you MUST understand the context first.
Checklist
You MUST complete these steps in order:
- Read the relevant code — understand existing implementation, patterns, dependencies
- Understand the task — what exactly needs to be built or fixed
- Ask clarifying questions — one at a time, resolve ambiguities before writing code
- Plan the implementation — identify files to change, approach to take
- Write the code — clean, consistent with existing patterns, well-tested
- Test the change — run existing tests, add new tests for new behavior
- Verify it works — sanity check the full flow
Process Flow
Read relevant code
│
v
Understand the task
│
v
Ask clarifying questions (one at a time)
│
v
Plan implementation (files, approach)
│
v
Write the code
│
v
Write/run tests
│
v
Verify it works
The Process
Reading the relevant code:
- Read the files you'll be modifying and the files that depend on them
- Understand the existing patterns — naming, error handling, file structure
- Check existing tests to understand expected behavior
- Look at similar implementations in the codebase for reference
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.
- 9d ago First seen · 154 lines · 31 tokens per session scan A 3cc7ede75963
sde is a skill published in the GitHub repository Jaan-Mustafa/10x-Team (11 stars, last pushed 2mo ago), licensed MIT. It adds 31 tokens to every session and 1,647 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
Reproducibility Standards
Seeding, dependency pinning, environment capture, and data versioning for fully reproducible ML workflows.
your-skill-name
One sentence: what this skill does and when to invoke it. Use for: [list 2-3 trigger phrases users would naturally type].
claude-md-improver
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.