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/ptmrio/autorename-pdf/testnpx skills add ptmrio/autorename-pdf --skill testgit clone --depth 1 https://github.com/ptmrio/autorename-pdfWrote 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/ptmrio/autorename-pdf/test)<a href="https://agentmods.dev/skills/ptmrio/autorename-pdf/test"><img src="https://agentmods.dev/badge/skills/ptmrio/autorename-pdf/test.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.00020 | $0.00268 |
| Opus 5 | $0.00010 | $0.00134 |
| Sonnet 5 | $0.00004 | $0.00054 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
test 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 5d 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
Run Tests
Run the project test suite using pytest.
Steps
- Activate the venv before running any commands:
source venv/Scripts/activate
- Run tests with coverage:
python -m pytest tests/ -v --tb=short --cov=. --cov-report=term-missing
- If an argument is provided (e.g.,
test_document_processing), run only that test file:
python -m pytest tests/test_<argument>.py -v --tb=short
- Report results to the user:
- Number of tests passed/failed/skipped
- Coverage percentage for key modules
- If failures: show the failing test name and assertion error
If Tests Fail
- Read the failing test to understand what's expected
- Read the source module being tested
- Identify the root cause and suggest a fix
- Do NOT modify tests to make them pass unless the test itself is wrong
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.
- 5d ago First seen · 47 lines · 20 tokens per session scan A 8e0b180ebacf
test is a skill published in the GitHub repository ptmrio/autorename-pdf (116 stars, last pushed 15d ago), licensed MIT. It adds 20 tokens to every session and 268 once invoked, about $0.0001 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
test-manager
Review and improve automated tests for NestJS modules, contracts, and critical flows. Use when changing services, controllers, guards, repositories, billing, wallet, execution, or auth behavior.
unit-test-planner
Plan test coverage by layer, risk, and behavior. Use when adding features, fixing regressions, or deciding what to test in domain, data, UI, and integration layers.
unit-test-generator
Convert changed behavior into focused unit and integration test cases.
developer
Engineering templates for review, testing, refactoring, architecture, releases, and incidents.
ai-management-toolkit
Practical toolkit for small-team managers. Use when the user wants help planning weekly team work, running meetings, diagnosing blockers, giving feedback, coaching employees, making SWOT/5W2H/root-cause/PDCA decisions, reviewing performance, running one-on-ones, breaking work into SMART goals and WBS tasks, balancing…
testing-strategy
Design test strategies and test plans. Trigger with "how should we test", "test strategy for", "write tests for", "test plan", "what tests do we need", or when the user needs help with testing approaches, coverage, or test architecture.