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 skills/priyanshuchawda/codeaudit/refactor-with-testsnpx skills add priyanshuchawda/codeaudit --skill refactor-with-testsgit clone --depth 1 https://github.com/priyanshuchawda/codeauditWrote 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/priyanshuchawda/codeaudit/refactor-with-tests)<a href="https://agentmods.dev/skills/priyanshuchawda/codeaudit/refactor-with-tests"><img src="https://agentmods.dev/badge/skills/priyanshuchawda/codeaudit/refactor-with-tests.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 | $0.00030 | $0.00166 |
| Opus 5 | $0.00015 | $0.00083 |
| Sonnet 5 | $0.00006 | $0.00033 |
| Haiku 4.5 | $0.00003 | $0.00017 |
Grade A, and why
refactor-with-tests 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
Refactor With Tests
Workflow
- Identify the exact behavior to preserve.
- Add or locate tests that cover the behavior.
- Make the smallest useful refactor.
- Run relevant tests and typecheck.
- Update docs only when behavior, architecture, or setup changes.
- Summarize changed files and validation.
Guardrails
- Do not combine unrelated refactors.
- Do not rename public APIs without an explicit migration reason.
- Do not weaken validation, auth, error handling, or observability to simplify code.
- Preserve user changes in a dirty worktree.
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 · 25 lines · 30 tokens per session scan A 9cf87f17752a
refactor-with-tests is a skill published in the GitHub repository priyanshuchawda/codeaudit (1 stars, last pushed 4mo ago), licensed MIT. It adds 30 tokens to every session and 166 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-31.
Other skills, from other repositories
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
backend/testing-guide
后端测试编写指南，包括单元测试、集成测试和E2E测试的编写方法和最佳实践.
qa/test-strategy
测试策略和测试金字塔原则，定义单元测试、集成测试、E2E测试的分布和覆盖要求.
test-patterns
Applies proven testing patterns — Arrange-Act-Assert (AAA), Given-When-Then, Test Data Builders, Object Mother, parameterized tests, fixtures, spies, and test doubles — to help write maintainable, reliable, and readable test suites. Use when the user asks about writing unit tests, integration tests, or end-to-end…
pm-tests
List missing unit-test companions for core/changed sources. Do not write tests into the business tree unless the user confirms.
coverage
Compute code coverage for active track or module. Targets 95%+ coverage with report and justification for uncovered lines. Complements TDD workflow.