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 furkangonel/cowrangler --skill plangit clone --depth 1 https://github.com/furkangonel/cowranglerWrote 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/furkangonel/cowrangler/plan)<a href="https://agentmods.dev/skills/furkangonel/cowrangler/plan"><img src="https://agentmods.dev/badge/skills/furkangonel/cowrangler/plan.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.00013 | $0.01953 |
| Opus 5 | $0.00006 | $0.00977 |
| Sonnet 5 | $0.00003 | $0.00391 |
| Haiku 4.5 | $0.00001 | $0.00195 |
Grade A, and why
plan 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 6d 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Planning SOP
A structured process for understanding what to build, how to build it, and what could go wrong — before writing a single line of production code.
When to Use
- User wants to plan a new feature before implementing it
- User needs to design a system or subsystem from scratch
- User wants to break down a complex task into implementable steps
- User needs to make and record an architecture decision
- User is unsure where to start on a non-trivial problem
The Planning Process
1. UNDERSTAND → 2. EXPLORE → 3. DESIGN → 4. DECOMPOSE → 5. RISK
Do not skip steps. Each phase has a defined output.
Phase 1 — Understand
Goal: Nail down what "done" looks like before touching the design.
Questions to answer:
- What problem does this solve? (user story or job-to-be-done)
- Who are the users and what do they need to do?
- What are the explicit success criteria? (how do we know this is working?)
- What are the explicit constraints? (budget, timeline, stack, team size, compliance)
- What is explicitly OUT of scope?
- Is there an existing system this must integrate with?
Output template:
## Problem Statement
[One paragraph: who has this problem, what is the problem, what is the impact]
## Success Criteria
- [ ] User can do X in under Y seconds
- [ ] System handles Z requests/sec without degradation
- [ ] Error rate < 0.1% for operation W
## Constraints
- Must use existing PostgreSQL database
- Must deploy on current Kubernetes cluster
- No new external service dependencies without security review
## Out of Scope
- Admin panel (separate ticket)
- Mobile app changes (v2)
Phase 2 — Explore
Goal: Understand the existing system before proposing changes.
Actions:
- Read relevant existing code (don't rely on memory)
- Identify all call sites for code being changed
- Map data flows: where does the data come from, where does it go?
- Check for related tests — understand the existing contract
- Read any existing ADRs or design docs for context
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.
- 6d ago First seen · 239 lines · 13 tokens per session scan A d750d1ecce62
plan is a skill published in the GitHub repository furkangonel/cowrangler (2 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 1,953 once invoked, about $0.0001 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-31.
Other skills, from other repositories
genui
Render structured, glanceable, interactive UI in the chat instead of plain text — dashboards, stat cards, filterable tables, charts, mermaid diagrams, choice panels, forms, quizzes. Panels can carry an id so later turns update them in place, and most interaction resolves in the browser with no round-trip. Read this…
artifact-design
Design guidance for any self-contained HTML/Markdown file shown in octo's Artifacts panel — reports, dashboards, architecture/system diagrams, generated UIs, slide-style pages. Read this BEFORE writing the file, not after — it calibrates how much design effort the request warrants and covers the panel's real…
ppt-orchestrator
A dispatcher for creating presentations, slide decks, long images, and weekly reports. It chooses a visual style and output format, then sends the work to a more specialised add-on.
anycap-human-interaction
Collect structured visual feedback from humans using AnyCap's annotation tool, or create and iterate on diagrams using the interactive whiteboard (Excalidraw). Covers image annotation, URL/web page review with screen recording, video review, audio feedback, and collaborative diagramming with Mermaid input. Use when…
zhongguose-html-skill
An HTML-only presentation system using traditional Chinese colours and Chinese-style visual design. It helps organise source material into a report structure and produces a self-contained HTML file with its assets.
storyboard-generation
Rules and prompts for generating structured presentation slides and multi-panel storyboards.