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/kendex-issuesnpx skills add vanillagreencom/kendex --skill kendex-issuesgit clone --depth 1 https://github.com/vanillagreencom/kendexWrote 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/vanillagreencom/kendex/kendex-issues)<a href="https://agentmods.dev/skills/vanillagreencom/kendex/kendex-issues"><img src="https://agentmods.dev/badge/skills/vanillagreencom/kendex/kendex-issues.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 | $0.00025 | $0.02314 |
| Opus 5 | $0.00013 | $0.01157 |
| Sonnet 5 | $0.00005 | $0.00463 |
| Haiku 4.5 | $0.00003 | $0.00231 |
Grade C, and why
kendex-issues scanned grade C with 1 finding 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 today.
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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- kendex:project-instructions:start --> How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Instructions
Problems with a kendex-owned skill go through kendex report; check ownership in the file first.
kendex Issue Steward
watch → poll → triage → fix → merge → propagate → reschedule. One cycle per turn.
| Concern | Owning skill |
|---|---|
| Fix cycle (prepare → delegate → review → submit → merge) | orch |
| PR threads, replies, reviews, merges, CI logs | github |
| Watching open PRs | review-gate pr-watch.sh |
| Linear reads and writes | linear |
Hand-rolled PR mechanics (raw gh api where a github.sh command exists)
are a defect.
Loop (one turn)
- PR watch:
GH_REPO=vanillagreencom/kendex .agents/skills/review-gate/scripts/pr-watch.sh. Silence + exit 0 = nothing needs you. Attention lines → act through the github skill. After a gate-green, also checkisInMergeQueue+autoMergeRequest(GraphQL). Queue ejection is silent: re-arm once; a second ejection is a flaky required suite. Quarantine, never re-arm loops. - Poll Linear:
linear.sh sync --reconcile, thenlinear.sh cache issues list --state "Triage,Backlog,Todo,In Progress" --max. Linear is the complete queue (GitHub→Linear sync is one-way); Triage holds the GitHub-synced arrivals. Cross-checkgh issue list --repo vanillagreencom/kendex --state open: an open GH issue whose Linear mirror is Done is residue, so close it naming the PR; one with no mirror means the sync broke, so triage it from GitHub and say so. Nothing on either surface → reschedule. - Triage each issue (below); run the fix cycle for each valid defect.
Mutate on the issue's home surface: GH-mirrored issues (Linear body links
the GH issue) are closed/commented on GitHub; Linear-native ones through
the linear skill. PR body carries
Closes KEN-<n>plusCloses #<n>when a mirror exists. - After any merge, propagate.
- Reschedule (Cadence). Stop only if the user asked.
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.
- today Changed · +8 lines scan A → C a18abc26ce62
- yesterday Changed · +2 lines 7741e144cd34
- 4d ago First seen · 160 lines · 25 tokens per session scan A 878a64580d85
kendex-issues is a skill published in the GitHub repository vanillagreencom/kendex (66 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 2,314 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). 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.