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-deploy)<a href="https://agentmods.dev/commands/venkateshvenki404224/frappe-apps-manager/frappe-deploy"><img src="https://agentmods.dev/badge/commands/venkateshvenki404224/frappe-apps-manager/frappe-deploy/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-deploy"><img src="https://agentmods.dev/badge/commands/venkateshvenki404224/frappe-apps-manager/frappe-deploy.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.00008 | $0.00381 |
| Opus 5 | $0.00004 | $0.00191 |
| Sonnet 5 | $0.00002 | $0.00076 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade B, and why
frappe-deploy scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Restart services: `sudo supervisorctl restart all` or `bench restart` What it actually says
Frappe Deploy Command
Guide deployment of Frappe applications to production:
- Pre-deployment checklist:
- Verify all changes are committed to git
- Ensure migrations are tested
- Check for breaking changes
- Confirm backup exists
- Review security settings
- Environment verification:
- Confirm target environment (staging/production)
- Check SSH access to production server
- Verify bench directory on production
- Deployment preparation:
- Ask about deployment method:
- Git pull and migrate
- Full bench update
- Specific app update
- Ask about downtime window
- Confirm maintenance mode preference
- Ask about deployment method:
- Deployment steps:
- Enable maintenance mode:
bench --site <site-name> set-maintenance-mode on - Pull latest changes:
git pullin app directory - Install dependencies:
bench setup requirements - Run migrations:
bench --site <site-name> migrate - Build assets:
bench build --app <app-name> - Clear cache:
bench --site <site-name> clear-cache - Restart services:
sudo supervisorctl restart allorbench restart - Disable maintenance mode:
bench --site <site-name> set-maintenance-mode off
- Enable maintenance mode:
- Post-deployment verification:
- Check site is accessible
- Verify key functionality
- Check error logs
- Monitor performance
- Rollback plan: Provide rollback instructions if issues occur:
- Revert git commits
- Restore from backup
- Previous version migration
Production safety: Emphasize testing in staging first, backing up before deployment, and having a rollback plan ready.
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 · 46 lines · 8 tokens per session scan B 9168db4036b6
frappe-deploy is a command published in the GitHub repository Venkateshvenki404224/frappe-apps-manager (27 stars, last pushed 3mo ago), licensed MIT. It adds 8 tokens to every session and 381 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). 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.