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/Dkm0315/frappe-agentWrote 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/dkm0315/frappe-agent/frappe-drive)<a href="https://agentmods.dev/commands/dkm0315/frappe-agent/frappe-drive"><img src="https://agentmods.dev/badge/commands/dkm0315/frappe-agent/frappe-drive/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/dkm0315/frappe-agent/frappe-drive"><img src="https://agentmods.dev/badge/commands/dkm0315/frappe-agent/frappe-drive.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.00000 | $0.00074 |
| Opus 5 | $0.00000 | $0.00037 |
| Sonnet 5 | $0.00000 | $0.00015 |
| Haiku 4.5 | $0.00000 | $0.00007 |
Grade A, and why
frappe-drive 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 10d 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 Drive
Treat the task as Frappe Drive work.
- Identify file/folder ownership, sharing, visibility, storage, previews, indexing, retention, and linked records.
- Preserve file permission checks and avoid exposing private paths or signed URLs too broadly.
- Keep file metadata, sharing state, linked record, recent activity, and primary actions visible.
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.
- 10d ago First seen · 8 lines · 0 tokens per session scan A 0194f3b290ed
frappe-drive is a command published in the GitHub repository Dkm0315/frappe-agent (24 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 74 tokens. 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
sdd-apply
Implement SDD tasks — writes code following specs and design.
sdd-explore
Explore and investigate an idea or feature — reads codebase and compares approaches.
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
gentle-sdd-ff
Fast-forward all SDD planning phases — proposal through tasks.
icpg-bootstrap
Infer ReasonNodes from existing git commit history. One-time setup for existing codebases.
ijfw-audit
Run the IJFW audit gate for the current workflow phase. Usage: /ijfw-audit [phase name].