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 agentmods add commands/dkm0315/frappe-agent/frappe-fullstackgit 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-fullstack)<a href="https://agentmods.dev/commands/dkm0315/frappe-agent/frappe-fullstack"><img src="https://agentmods.dev/badge/commands/dkm0315/frappe-agent/frappe-fullstack.svg" alt="Measured on agentmods" 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.00075 |
| Opus 5 | $0.00000 | $0.00037 |
| Sonnet 5 | $0.00000 | $0.00015 |
| Haiku 4.5 | $0.00000 | $0.00007 |
Grade A, and why
frappe-fullstack 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 5d 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 Fullstack
Act as a Frappe full-stack specialist.
- Inspect bench, site, app, and customization context first.
- Decide whether the change belongs in configuration, metadata, customization DocTypes, backend code, frontend code, or bench operations.
- Keep Python and JavaScript responsibilities explicit.
- Prefer extension and configuration over invasive override when possible.
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.
- 5d ago First seen · 9 lines · 0 tokens per session scan A e15176bfd947
frappe-fullstack is a command published in the GitHub repository Dkm0315/frappe-agent (23 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 75 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
ctx
Run a full context hygiene audit: discover all AI context files, check for staleness, and detect cross-tool drift.
ctx-drift
Find contradictions, gaps, and inconsistencies between AI context files from different tool ecosystems.
ctx-check
Validate claims in AI context files against the actual codebase to find stale, broken, and drifted references.
ctx-discover
Scan the repository and inventory all AI context files across tool ecosystems.
skillrx
Scan AI agent plugin or skill for malicious patterns before install.
checklist
Generate a custom checklist for the current feature based on user requirements.