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-install-app)<a href="https://agentmods.dev/commands/venkateshvenki404224/frappe-apps-manager/frappe-install-app"><img src="https://agentmods.dev/badge/commands/venkateshvenki404224/frappe-apps-manager/frappe-install-app/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-install-app"><img src="https://agentmods.dev/badge/commands/venkateshvenki404224/frappe-apps-manager/frappe-install-app.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.00009 | $0.00263 |
| Opus 5 | $0.00005 | $0.00131 |
| Sonnet 5 | $0.00002 | $0.00053 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
frappe-install-app 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.
What it actually says
Frappe Install App Command
Install a Frappe application to a specific site:
- Verify bench directory: Confirm we're in a Frappe bench directory
- List available apps: Show apps that are available in the bench but may not be installed on the site
- List available sites: Display all sites in the bench
- Get installation details:
- App name to install
- Site name where the app should be installed
- Pre-installation checks:
- Verify the app exists in the bench
- Verify the site exists
- Check if the app is already installed (warn user)
- Install the app: Run
bench --site <site-name> install-app <app-name> - Verify installation:
- Check that the app appears in the site's installed apps
- Look for any error messages
- Post-installation:
- Suggest running migrations if needed
- Recommend restarting bench
- Provide next steps for using the app
Error handling: Provide clear error messages if installation fails, including common issues like missing dependencies or database connection problems.
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 · 29 lines · 9 tokens per session scan A a4804b2eaaae
frappe-install-app is a command published in the GitHub repository Venkateshvenki404224/frappe-apps-manager (27 stars, last pushed 3mo ago), licensed MIT. It adds 9 tokens to every session and 263 once invoked, about $0.0000 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.