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 SecondLifes/delphi-expert --skill pythongit clone --depth 1 https://github.com/SecondLifes/delphi-expertWrote 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/secondlifes/delphi-expert/python)<a href="https://agentmods.dev/skills/secondlifes/delphi-expert/python"><img src="https://agentmods.dev/badge/skills/secondlifes/delphi-expert/python/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/secondlifes/delphi-expert/python"><img src="https://agentmods.dev/badge/skills/secondlifes/delphi-expert/python.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.00067 | $0.00763 |
| Opus 5.5 | $0.00027 | $0.00305 |
| Sonnet 5.5 | $0.00013 | $0.00153 |
| Haiku 4.5 | $0.00007 | $0.00076 |
Grade A, and why
python 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- python — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Python
Consolidated from three separately-sourced skills (wshobson/agents:
python-performance-optimization, python-testing-patterns,
python-design-patterns — reviewed for correctness, no issues found)
into one, per this workspace's "one skill per topic" policy.
When to Use
- Writing an ad-hoc Python script to accomplish a task (data processing, file manipulation, automation, validation)
- Identifying and fixing performance bottlenecks (CPU, memory, I/O)
- Writing or reviewing tests (unit, integration, async, property-based)
- Designing a new component/service or refactoring a tangled one
- Deciding between inheritance and composition, or whether to add an abstraction
Usage
| You say | What happens |
|---|---|
"Write a script to parse these CSVs" / ad-hoc helper script request |
Applies the Golden Rules directly (simplicity first, single responsibility) — no reference file needed for a small script. |
"This function is slow, why?" / "Bu kodu optimize et" |
Loads references/performance.md — profiles with cProfile/py-spy first, then applies the matching optimization pattern. |
"Write tests for this" / "Şunun için pytest yaz" |
Loads references/testing.md — fixtures, mocking, async tests, property-based testing as the case requires. |
"Refactor this class" / "Composition mi inheritance mi kullanmalıyım?" |
Loads references/design-patterns.md — SRP, composition-over-inheritance, Rule of Three, dependency injection. |
Golden Rules
- Profile before optimizing. Measure with
cProfile/py-spyfirst — don't guess at bottlenecks. - Simplicity first (KISS). Choose the simplest solution that works; complexity must be justified by concrete requirements.
- Single Responsibility. Each function/class has one reason to change — separate HTTP parsing, business logic, and data access.
- Compose, don't inherit for flexibility and testability; inject dependencies through constructors.
- Rule of Three — don't abstract until you have three real instances of the duplication; a wrong abstraction is worse than repetition.
- Test in isolation. Fakes/mocks for external dependencies; never hit a real database in unit tests.
- Use built-ins and generators for large datasets; prefer
dict/setlookups over list scans.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 47 lines · 67 tokens per session scan A 85ae1ce2af1d
python is a skill published in the GitHub repository SecondLifes/delphi-expert (3 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 763 once invoked, about $0.0003 per session on Opus 5.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
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
python-testing
Guidelines for writing and running tests in the Agent Framework Python codebase. Use this when creating, modifying, or running tests.
adk-verify-snippets
Checks that every Python code block in a Markdown file actually compiles and runs, by extracting each block to a temporary file, executing it in an isolated subprocess, and writing a pass/fail report with per-snippet coverage. Use when the user asks to verify, test, or validate the code samples in a README, a guide…
adk-setup
Sets up a local ADK Python development environment in a git clone of the open-source adk-python repository: a uv virtual environment, all dependency extras, pre-commit hooks, and a first unit-test run. Runs only when explicitly requested, never on its own. Use when asked to set up, bootstrap, or repair a development…
test-generator
Generate pytest test cases for Python functions and classes.
typescript
TypeScript strict mode with eslint and jest.