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-gameplangit 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-gameplan)<a href="https://agentmods.dev/skills/dkm0315/frappe-agent/frappe-gameplan"><img src="https://agentmods.dev/badge/skills/dkm0315/frappe-agent/frappe-gameplan/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-gameplan"><img src="https://agentmods.dev/badge/skills/dkm0315/frappe-agent/frappe-gameplan.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.00051 | $0.00244 |
| Opus 5 | $0.00026 | $0.00122 |
| Sonnet 5 | $0.00010 | $0.00049 |
| Haiku 4.5 | $0.00005 | $0.00024 |
Grade A, and why
frappe-gameplan 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 Gameplan specialist.
First clarify:
- whether the object is a project, task, discussion, decision, note, milestone, or team workspace
- team membership, visibility, ownership, and notification needs
- whether the process is lightweight collaboration or needs formal ERPNext project/accounting integration
Prefer configuration and metadata before code:
- workspace setup, permissions, custom fields, status/workflow metadata, notifications, reports, dashboards, and integrations
- links to ERPNext Project, Task, Issue, or Timesheet only when the operating process needs those records
When implementing:
- keep discussion, task state, decisions, and project delivery data separate
- preserve async collaboration history and avoid destructive edits to comments, decisions, or audit trails
- be careful with cross-team visibility and private workspaces
For UX, make ownership, due dates, blockers, recent decisions, and unread or pending activity easy to scan.
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 · 23 lines · 51 tokens per session scan A 2e77a386c84c
frappe-gameplan is a skill published in the GitHub repository Dkm0315/frappe-agent (24 stars, last pushed 5d ago), licensed MIT. It adds 51 tokens to every session and 244 once invoked, about $0.0003 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
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
workspace
Dynamic multi-repo and monorepo awareness for Claude Code. Analyze workspace topology, track API contracts, and maintain cross-repo context.
ticket-craft
Create Jira/Asana/Linear tickets optimized for Claude Code execution - AI-native ticket writing.
team-coordination
Multi-person projects - shared state, todo claiming, handoffs.