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.
git clone --depth 1 https://github.com/Venkateshvenki404224/frappe-apps-managerWrote 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/commands/venkateshvenki404224/frappe-apps-manager/frappe-test)<a href="https://agentmods.dev/commands/venkateshvenki404224/frappe-apps-manager/frappe-test"><img src="https://agentmods.dev/badge/commands/venkateshvenki404224/frappe-apps-manager/frappe-test/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/commands/venkateshvenki404224/frappe-apps-manager/frappe-test"><img src="https://agentmods.dev/badge/commands/venkateshvenki404224/frappe-apps-manager/frappe-test.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.00013 | $0.02928 |
| Opus 5 | $0.00006 | $0.01464 |
| Sonnet 5 | $0.00003 | $0.00586 |
| Haiku 4.5 | $0.00001 | $0.00293 |
Grade A, and why
frappe-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 12d 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 — 500 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frappe Test Command
Execute comprehensive tests for Frappe applications including unit tests, integration tests, and generate coverage reports.
Steps to Execute
1. Verify Test Environment
- Check if current directory is a valid Frappe bench
- Verify bench command is available
- Check if site exists for testing
- Ensure test dependencies are installed:
pip install coverage pytest
2. Determine Test Scope
Ask user what they want to test:
A. Specific DocType
- App name
- Module name
- DocType name
- Example:
test_[doctype_name].py
B. Specific App
- App name only
- Tests all modules in the app
C. All Apps
- Run complete test suite
- May take significant time
D. Specific Test File/Function
- Full path to test file
- Optional: specific test function name
3. Test Execution Options
Offer test configuration options:
Basic Options:
--verbose: Show detailed test output--failfast: Stop on first failure--profile: Profile test execution time
Coverage Options:
--coverage: Generate coverage report--html-coverage: Generate HTML coverage report- Coverage threshold (warning if below X%)
Test Filtering:
- Run specific test methods
- Skip certain tests
- Test by markers/tags
4. Run Tests
Execute appropriate test command based on scope:
Test Specific DocType:
bench --site [site-name] run-tests \
--app [app-name] \
--doctype "[DocType Name]" \
[--verbose] \
[--coverage]
Test Specific App:
bench --site [site-name] run-tests \
--app [app-name] \
[--module [module-name]] \
[--verbose] \
[--coverage]
Test All Apps:
bench --site [site-name] run-tests \
[--verbose] \
[--coverage]
Test Specific File:
bench --site [site-name] run-tests \
--test [path/to/test_file.py] \
[--verbose]
Test with Coverage:
bench --site [site-name] run-tests \
--app [app-name] \
--coverage \
--coverage-report-html
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.
- 12d ago First seen · 500 lines · 13 tokens per session scan A 67cc14b593d9
frappe-test is a command published in the GitHub repository Venkateshvenki404224/frappe-apps-manager (27 stars, last pushed 3mo ago), licensed MIT. It adds 13 tokens to every session and 2,928 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 commands, from other repositories
test-tdd
Run when user calls /test-tdd. Scans modified files, locates their corresponding unit/integration test suites, and runs them.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
lg:node
Create, modify, and manage nodes in LangGraph graphs including LLM nodes, tool nodes, human-in-the-loop, subgraphs, and conditional nodes.
test
Execute a comprehensive test run for the following target.
implement-fix
Minimal pipeline for test-fixing tasks.
unity-test
Writes missing tests and runs them via MCP. Identifies untested code, creates EditMode/PlayMode tests, executes via runtests, reports results.