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 skills/vanillagreencom/kendex/devnpx skills add vanillagreencom/kendex --skill devgit clone --depth 1 https://github.com/vanillagreencom/kendexWhat 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 | $0.00016 | $0.01464 |
| Opus 5 | $0.00008 | $0.00732 |
| Sonnet 5 | $0.00003 | $0.00293 |
| Haiku 4.5 | $0.00002 | $0.00146 |
Grade A, and why
dev 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 yesterday.
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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Workflows
Problem with this skill? Run
kendex report— it files to the owning repo automatically. Do not hand-file.
orch is the caller and runtime: it owns delegation format, round acceptance, and every shell-shape rule.
| Workflow | Purpose |
|---|---|
workflows/dev-implement.md |
Implementation: activate → plan → implement → validate → commit → QA labels → summary → artifact → return (§ 1-11) |
workflows/dev-fix.md |
Review fixes: evaluate → apply or skip → validate → commit → artifact → return |
Review and QA-review belong to the reviewer skill: ../reviewer/workflows/review.md, ../reviewer/workflows/qa-review.md. Command shapes, literal format tags, and round mechanics are orch's: ../orch/SKILL.md § Harness-Safe Shell, § Format Tags Are Literal, § Round Closure.
Engineering Rules
- Scope is the reported symptom. Every behavioral surface a change touches must trace to a line in the report — if you cannot name that line, keep it out of this change. Two exceptions: mechanical enablers of landing it (locks, changelog, baselines, dismissal renewals) ride without a line, and a defect the change introduces or arms is in scope by definition.
- Prefer deleting code to abstracting it. Three similar lines beat a premature abstraction. A new dependency needs a one-line justification in its commit message.
- Every behavior change ships with a test that fails without it.
- An
elsethat "shouldn't happen" is a bug: assert or return an error, never continue silently. - Plain words over jargon: name things by what they do. Comments say why, never what or when — no temporal markers, no references to the change that wrote them. Commit bodies explain intent, never narrate the diff.
- Delete unused code completely — no compat shims, no
_renamedvars, no "removed" comments. - Never re-implement a judgment another component owns — delegate. Delegation impossible = design escalation in your return, never a twin.
- Stale docs are bugs: contradicting a committed doc means updating it in the same change.
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- kendex.settings.toml.example 459 B
- README.md 2.1 KB
- tests/decider-issue-lookup-lint.test.sh 1.5 KB runs code
- tests/handoff-body-file-lint.test.sh 2.2 KB runs code
- tests/linear-cache-preflight-contract.test.sh 5.8 KB runs code
- tests/qa-label-preflight-contract.test.sh 1.6 KB runs code
- workflows/dev-fix.md 5.4 KB
- workflows/dev-implement.md 17 KB
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.
- yesterday First seen · 73 lines · 16 tokens per session scan A 0cfba453f778
dev is a skill published in the GitHub repository vanillagreencom/kendex (65 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 1,464 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-30.
Other skills, from other repositories
surf
Control Chrome browser via CLI for testing, automation, and debugging. Use when the user needs browser automation, screenshots, form filling, page inspection, network/CPU emulation, DevTools streaming, or AI queries via ChatGPT/Gemini/Perplexity/Grok/AI Studio.
prose-review
Review prose written for others -- user-facing docs, prompts for other LLMs, inline comments, docstrings, and other-facing messages -- for local jargon leakage, orphaned references, missing grounding, and audience or genre misfit.
text-search
Search indexed text corpora with qmd. For indexed content, prefer qmd over grep.
repoprompt-tool-guidance-refresh
Refresh RepoPrompt tool guidance when the CLI/MCP surface changes. Tracks RepoPrompt CE (rpce-cli, the maintained target) across versions, and can diff the frozen Classic CLI (rp-cli) against CE. Uses /.pi/agent/skills/repoprompt-tool-guidance-refresh/scripts/track-rp-version.sh to capture/diff --help and -l (tool…
xcodebuildmcp
Build/test Xcode projects via the XcodeBuildMCP MCP server using a local CLI wrapper for pi (no MCP support). Use when the user mentions Xcode, xcodebuild, iOS builds/tests, or XcodeBuildMCP.
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.