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 lubusIN/frappe-skills --skill testinggit clone --depth 1 https://github.com/lubusIN/frappe-skillsWrote 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/lubusin/frappe-skills/testing)<a href="https://agentmods.dev/skills/lubusin/frappe-skills/testing"><img src="https://agentmods.dev/badge/skills/lubusin/frappe-skills/testing/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/lubusin/frappe-skills/testing"><img src="https://agentmods.dev/badge/skills/lubusin/frappe-skills/testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00042 | $0.01601 |
| Opus 5 | $0.00021 | $0.00800 |
| Sonnet 5 | $0.00008 | $0.00320 |
| Haiku 4.5 | $0.00004 | $0.00160 |
Grade A, and why
testing 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 11d 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frappe Testing
Write and run tests for Frappe applications using the built-in testing framework.
When to use
- Writing unit tests for DocType controllers
- Writing integration tests for workflows and APIs
- Running existing test suites
- Debugging test failures
- Setting up CI pipelines for Frappe apps
Inputs required
- App name to test
- Site name for test execution
- Specific module/DocType to test (optional)
- Test environment (dev site, dedicated test site)
Procedure
0) Setup test environment
# Install dev dependencies
bench setup requirements --dev
# Ensure site is ready
bench --site <site> migrate
1) Run tests
# Run all tests for an app
bench --site <site> run-tests --app my_app
# Run tests for specific module
bench --site <site> run-tests --module my_app.my_module.tests
# Run tests for specific DocType
bench --site <site> run-tests --doctype "My DocType"
# Verbose output
bench --site <site> run-tests --app my_app -v
# Run single test file
bench --site <site> run-tests --module my_app.doctype.sample_doc.test_sample_doc
2) Write DocType tests
Create test_<doctype_name>.py alongside the DocType:
# my_app/doctype/sample_doc/test_sample_doc.py
import frappe
from frappe.tests.utils import FrappeTestCase
class TestSampleDoc(FrappeTestCase):
def setUp(self):
# Create test data
self.doc = frappe.get_doc({
"doctype": "Sample Doc",
"title": "Test Document"
}).insert()
def tearDown(self):
# Cleanup
frappe.delete_doc("Sample Doc", self.doc.name, force=True)
def test_creation(self):
self.assertEqual(self.doc.title, "Test Document")
def test_validation(self):
doc = frappe.get_doc({
"doctype": "Sample Doc",
"title": "" # Invalid - required field
})
self.assertRaises(frappe.ValidationError, doc.insert)
def test_workflow(self):
self.doc.status = "Approved"
self.doc.save()
self.assertEqual(self.doc.status, "Approved")
What ships with it
5 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.
- 11d ago First seen · 229 lines · 42 tokens per session scan A 9bada8bad871
testing is a skill published in the GitHub repository lubusIN/frappe-skills (57 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 1,601 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
testing-setup
Analyze and create a testing strategy for native Android apps - install testing libraries, set up test infrastructure, create harnesses for unit tests, UI tests, screenshot tests, and end-to-end tests.
testing-strategies
Comprehensive testing strategy covering unit, integration, e2e, property-based, and mutation testing with practical patterns.
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.
frontend-testing
Comprehensive frontend testing strategy covering unit, integration, E2E, visual regression, and accessibility testing.
verify
Verification loop — lint -> typecheck -> unit -> integration -> e2e.
check-coverage
Comprehensive assessment of Unit / Integration / E2E three-layer test coverage, identify gaps and provide actionable recommendations.