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 Dkm0315/frappe-agent --skill frappe-drivegit 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/skills/dkm0315/frappe-agent/frappe-drive)<a href="https://agentmods.dev/skills/dkm0315/frappe-agent/frappe-drive"><img src="https://agentmods.dev/badge/skills/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/skills/dkm0315/frappe-agent/frappe-drive"><img src="https://agentmods.dev/badge/skills/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.00049 | $0.00239 |
| Opus 5 | $0.00024 | $0.00120 |
| Sonnet 5 | $0.00010 | $0.00048 |
| Haiku 4.5 | $0.00005 | $0.00024 |
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 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.
What it actually says
Act as a Frappe Drive specialist.
Start by identifying:
- file/folder ownership, sharing model, and visibility boundary
- whether files are standalone knowledge assets or attached to ERPNext/Frappe records
- storage, preview, indexing, retention, and audit requirements
- whether the change belongs in configuration, metadata, permissions, frontend, or storage/backend code
Prefer standard surfaces first:
- roles, sharing rules, custom fields, workflows, reports, dashboards, and record attachments
- built-in file APIs and attachment behavior before custom storage logic
When code is needed:
- preserve file permission checks and avoid exposing private paths or signed URLs too broadly
- keep storage, metadata, preview, sharing, and indexing concerns separate
- plan migrations carefully when moving or transforming stored files
For UX, prioritize file name, type, owner, location, sharing state, linked record, recent activity, and primary actions.
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 · 24 lines · 49 tokens per session scan A cbc9a1f5a970
frappe-drive is a skill published in the GitHub repository Dkm0315/frappe-agent (24 stars, last pushed 5d ago), licensed MIT. It adds 49 tokens to every session and 239 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
memstack-business-scope-of-work
Use this skill when the user says 'scope of work', 'SOW', 'define scope', 'project scope', 'write SOW', 'scope document', or is defining project boundaries, deliverables, and acceptance criteria for a formal engagement. Do NOT use for proposals, contracts, or invoicing.
memstack-business-invoice-generator
Use this skill when the user says 'invoice', 'generate invoice', 'create invoice', 'bill client', 'line items', 'payment terms', or needs professional invoices with tax calculations and payment instructions. Do NOT use for contracts or financial projections.
ring:creating-handoffs
Creating a handoff document that captures session state (completed work, decisions, open items, next steps) and delivering it via Plan Mode so the user gets the native 'clear context and continue implementing' resume option. Use when ending a session, when context grows large, or the user says 'handoff', 'save…
wheypoint
Mark the current conversation as a durable handoff so a new agent can resume the work. Use when the user wants to preserve state for a later or parallel session. Triggers include "hand this off", "write a handoff", "drop a wheypoint", "checkpoint this", "compact the conversation", and "/wheypoint". Also use for "wrap…
managing-artifacts
Artifact storage paths and project-encoded conventions for generated documents, reports, plans, and audits. Loaded by the core rule module. Triggers: 'where should I put this', 'save report', 'output directory'.
aside-notion
Read this skill when you need to use Notion. Don't have to open a browser tab.