Borrowing it
Nothing to install: this file belongs to saski/arnesto. 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/saski/arnesto/main/.agents/skills/xp-plan-untested-code/SKILL.mdgit clone --depth 1 https://github.com/saski/arnestoWrote 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/saski/arnesto/xp-plan-untested-code)<a href="https://agentmods.dev/skills/saski/arnesto/xp-plan-untested-code"><img src="https://agentmods.dev/badge/skills/saski/arnesto/xp-plan-untested-code.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.00039 | $0.00313 |
| Opus 5 | $0.00019 | $0.00156 |
| Sonnet 5 | $0.00008 | $0.00063 |
| Haiku 4.5 | $0.00004 | $0.00031 |
Grade A, and why
xp-plan-untested-code 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.
What it actually says
Senior XP Developer — Plan Tests for Untested Code
Act as a Senior XP Developer with Lean thinking. Work in small batches, prefer clarity, and improve reliability by expanding meaningful test coverage.
Task
Write a concise, actionable plan to create tests that exercise all untested code.
Focus on:
-
Identify gaps
- Use coverage analysis to list untested functions, branches, and edge cases.
- Classify them by risk and production impact.
-
Prioritize
- Address highest-risk paths first (complex logic, error handling, integrations).
- Defer low-value or dead code, calling it out explicitly.
-
Design tests
- Write small, behavior-focused tests.
- Cover edge cases, invalid inputs, and boundary conditions.
- Avoid over-mocking; keep intent clear.
-
Iterate
- Add one test at a time.
- Run tests, confirm they fail for the right reason, then implement if needed.
- Refactor both code and tests as clarity emerges.
-
Validate completeness
- Re-run coverage to confirm gaps are closed.
- Explain any cases intentionally left untested.
This plan should emphasize simplicity, flow, and evolvability while increasing confidence in production reliability.
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 · 37 lines · 39 tokens per session scan A f805163e8e54
xp-plan-untested-code is a skill published in the GitHub repository saski/arnesto (5 stars, last pushed today), licensed Unlicense. It adds 39 tokens to every session and 313 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-09-03.
Other skills, from other repositories
nemo-automodel-model-onboarding
Guide for onboarding new model architectures into NeMo AutoModel, including architecture discovery, implementation patterns, registration, and validation.
nemo-automodel-recipe-development
Create and modify NeMo AutoModel training and evaluation recipes, including YAML structure, builders, and execution flow.
mcore-testing
Test system for Megatron-LM. Covers test layout, recipe YAML structure, adding and running unit and functional tests, golden values, marker filters, and CI parity.
i4h-catheter-navigation-e2e
End-to-end smoke for catheter navigation covering setup, digital twin, DRR, and unit tests. Use when asked to run the full catheter workflow smoke or demo the v0.7 pipeline.
test-harness
Generates pytest test suites with happy path, edge cases, error conditions, fixture scaffolding, mocks, async patterns. Triggers on: "generate tests", "write tests for", "test this function", "create test suite", "pytest for", "unit tests for", "mock strategy for".
test-review
Test coverage review via Codex exec. Use when: reviewing test sufficiency, identifying coverage gaps, test quality audit. Not for: generating tests (use codex-test-gen), code review (use codex-code-review). Output: coverage analysis + gap report.