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 lubusIN/frappe-skills --skill project-triagegit clone --depth 1 https://github.com/lubusIN/frappe-skillsWrote 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/lubusin/frappe-skills/project-triage)<a href="https://agentmods.dev/skills/lubusin/frappe-skills/project-triage"><img src="https://agentmods.dev/badge/skills/lubusin/frappe-skills/project-triage/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/lubusin/frappe-skills/project-triage"><img src="https://agentmods.dev/badge/skills/lubusin/frappe-skills/project-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00046 | $0.00950 |
| Opus 5.5 | $0.00018 | $0.00380 |
| Sonnet 5.5 | $0.00009 | $0.00190 |
| Haiku 4.5 | $0.00005 | $0.00095 |
Grade A, and why
project-triage 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frappe Project Triage
Quickly analyze a Frappe project to determine its type, installed apps, version, and available tooling.
When to use
- First step when opening a new Frappe project
- Before making any code changes to understand the codebase
- When debugging to determine which apps/versions are involved
- To identify the development environment (Bench vs Frappe Manager)
Inputs required
- Project root path (where
apps/,sites/, or app code lives) - Access to run shell commands (for version checks)
Procedure
0) Identify project structure
Check for these patterns:
| Pattern | Project Type |
|---|---|
apps/ + sites/ directories |
Bench installation |
docker-compose.yml with frappe |
Frappe Manager site |
pyproject.toml or setup.py with frappe |
Standalone app |
doctype/ directory |
Inside an app module |
1) Detect installed apps
# Inside Bench/FM shell
bench --site <site> list-apps
# Or check apps directory
ls apps/
2) Check Frappe version
# Inside Bench/FM shell
bench version
# Or check from Python
bench --site <site> console
>>> frappe.__version__
3) Identify tooling
| File/Directory | Tooling |
|---|---|
Procfile |
Standard bench |
docker-compose.yml |
Docker/FM |
cypress/ |
UI testing available |
.github/workflows/ |
CI configured |
package.json with @frappe/* |
JS build tooling |
4) Check development mode
# Check site config
bench --site <site> console
>>> frappe.conf.developer_mode
Verification
- Project type identified (bench/FM/standalone app)
- Installed apps listed
- Frappe version known
- Development mode status confirmed
- Available tooling documented
Failure modes / debugging
- No site found: May be inside an app directory, navigate to bench root
- bench command not found: Not in bench environment, use
fm shellor activate venv - Permission errors: Check if running as correct user
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.
- 2mo ago First seen · 131 lines · 46 tokens per session scan A c90a03233371
project-triage is a skill published in the GitHub repository lubusIN/frappe-skills (68 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session and 950 once invoked, about $0.0002 per session on Opus 5.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.
project-triage compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| project-triagelubusIN/frappe-skills | Skill | 68 | 2d ago | MIT | A | 46 | Claude Code, Codex |
| build-mcp-serveranthropics/claude-plugins-official | Skill | 46k | yesterday | Apache-2.0 | A | 111 | Claude Code |
| data-manager-api-setupgoogle/skills | Skill | 22k | yesterday | Apache-2.0 | A | 86 | Claude Code, Codex |
| vss-manage-video-io-storageNVIDIA-AI-Blueprints/video-search-and-summarization | Skill | 2.0k | yesterday | Apache-2.0 | A | 143 | Claude Code, Codex |
| workers-best-practicescloudflare/skills | Skill | 3.3k | yesterday | Apache-2.0 | A | 25 | Claude Code |
| vss-search-archiveNVIDIA-AI-Blueprints/video-search-and-summarization | Skill | 2.0k | yesterday | Apache-2.0 | A | 67 | Claude Code, Codex |
| newclacky-ai/openclacky | Skill | 1.2k | yesterday | MIT | A | 10 | Claude Code |