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 ksmaster03/claude-canfly-skill --skill business-logic-specgit clone --depth 1 https://github.com/ksmaster03/claude-canfly-skillWrote 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/ksmaster03/claude-canfly-skill/business-logic-spec)<a href="https://agentmods.dev/skills/ksmaster03/claude-canfly-skill/business-logic-spec"><img src="https://agentmods.dev/badge/skills/ksmaster03/claude-canfly-skill/business-logic-spec/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/ksmaster03/claude-canfly-skill/business-logic-spec"><img src="https://agentmods.dev/badge/skills/ksmaster03/claude-canfly-skill/business-logic-spec.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.00113 | $0.03615 |
| Opus 5 | $0.00056 | $0.01808 |
| Sonnet 5 | $0.00023 | $0.00723 |
| Haiku 4.5 | $0.00011 | $0.00362 |
Grade A, and why
business-logic-spec 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 151 lines · 113 tokens per session scan A cd137d3e3c90
business-logic-spec is a skill published in the GitHub repository ksmaster03/claude-canfly-skill (14 stars, last pushed 28d ago), with no licence file. It adds 113 tokens to every session and 3,615 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session.
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.