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-doctype-design)<a href="https://agentmods.dev/commands/dkm0315/frappe-agent/frappe-doctype-design"><img src="https://agentmods.dev/badge/commands/dkm0315/frappe-agent/frappe-doctype-design/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-doctype-design"><img src="https://agentmods.dev/badge/commands/dkm0315/frappe-agent/frappe-doctype-design.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.00122 |
| Opus 5 | $0.00000 | $0.00061 |
| Sonnet 5 | $0.00000 | $0.00024 |
| Haiku 4.5 | $0.00000 | $0.00012 |
Grade A, and why
frappe-doctype-design 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
Frappe DocType Design
Handle this as Frappe DocType design work.
- Design the DocType as a human-facing form, not a flat field dump.
- Add only fields required by the actual use case.
- Use tabs, section breaks, and column breaks when they match the user's workflow.
- Group fields by mental model: overview, core details, people or links, schedule, finance, settings, and activity or audit when relevant.
- Keep primary required fields first and advanced or rare fields later.
- Avoid empty sections, vanity fields, duplicate fields, and speculative future fields.
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 · 11 lines · 0 tokens per session scan A 3c58f68d0767
frappe-doctype-design is a command published in the GitHub repository Dkm0315/frappe-agent (24 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 122 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
db-context-postgres
Validate that a generic Postgres database (GCP Cloud SQL, GKE Autopilot, self-hosted, etc.) is reachable via psql or pgdump, introspect a user-scoped subset of the schema (extensions, tables, columns, indexes, foreign keys, and optionally RLS policies and functions), and persist the result as DBCONTEXT.md inside the…
db-context-supabase
Validate that a Supabase MCP server is reachable, introspect a user-scoped subset of the database (tables, columns, types, RLS policies, optionally functions and recent migrations), and persist the result as DBCONTEXT.md inside the active task folder; adds a single.
db-migration
A guarded workflow for changing a database schema—the structure of tables and columns—including adding, removing, or updating stored data.
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
ijfw-audit
Run the IJFW audit gate for the current workflow phase. Usage: /ijfw-audit [phase name].
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.