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/robconery/kolea/githubnpx skills add robconery/kolea --skill githubgit clone --depth 1 https://github.com/robconery/koleaWhat 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.00083 | $0.01511 |
| Opus 5 | $0.00042 | $0.00756 |
| Sonnet 5 | $0.00017 | $0.00302 |
| Haiku 4.5 | $0.00008 | $0.00151 |
Grade A, and why
github 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.
This is a copy
100% identical to github — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub workflow
The point: write commits, issues, and PRs that read clearly weeks later. Be direct, be specific, skip the filler.
Branching — when to branch, when not
Trunk-based (commit straight to main) when:
- Single-file or single-concept fix.
- Typo, doc tweak, version bump, comment, lint fix.
- Test-only addition that doesn't change behavior.
- Anything that takes one commit and reviews itself in 30 seconds.
Short-lived branch when:
- More than ~2 commits expected.
- New feature or capability, even a small one.
- Schema/migration change.
- Anything that could break
mainfor someone else. - A spec / plan task that has its own id (e.g.
T052fromdocs/PLAN.md).
Branch naming: <type>/<short-slug> — type is one of
feat, fix, chore, docs, refactor, test. Examples:
feat/order-fulfillment-tx
fix/signature-verify-header-case
chore/bump-drizzle
Keep branches short-lived. Open the PR early, even as draft.
Commits — Conventional Commits, kept honest
Format:
<type>(<optional scope>): <imperative summary, lower-case, no period>
<body — what changed and why, wrapped at ~72 cols>
<footer — refs, breaking changes>
Types: feat, fix, chore, docs, refactor, test, perf,
build, ci, revert.
Summary line rules:
- 50 chars or fewer when possible, hard cap 72.
- Imperative mood (
add, notadded/adds). - No trailing period.
- Scope is optional; use it when there's an obvious area
(
feat(webhook): …,fix(db): …).
Body rules:
- Always include one if the change isn't self-evident from the diff.
- Explain what changed and why — never restate the diff line by line. Mention trade-offs or alternatives rejected if relevant.
- One blank line between summary and body.
- Reference issues with
Refs #123orCloses #123.
Footers:
Closes #Nto auto-close an issue on merge.BREAKING CHANGE: <what breaks, how to migrate>for breakages.Co-Authored-By:lines when pairing.
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 · 212 lines · 83 tokens per session scan A 6106a7e4b318
github is a skill published in the GitHub repository robconery/kolea (1 stars, last pushed 2d ago), licensed MIT. It adds 83 tokens to every session and 1,511 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to github, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
supermemory
Supermemory is a state-of-the-art memory and context infrastructure for AI agents. Use this skill when building applications that need persistent memory, user personalization, long-term context retention, or semantic search across knowledge bases. It provides Memory API for learned user context, User Profiles for…
moemail
Use when an AI agent needs a temporary/disposable email address — for receiving verification emails, testing email integrations, or any task requiring a temporary inbox via the moemail CLI.
moemail
Use when working in this repository and an AI agent needs a temporary/disposable email address through the MoeMail CLI.
create-saasmail-template
Write, validate, and create email templates for a saasmail instance — the full {{variable}} interpolation grammar, conditional/repeating {{#section}} rendering, HTML escaping, and the required-vs-optional send contract. Use this skill whenever the user is authoring or editing a saasmail email template, or asks…
saasmail-onboarding
Interactive setup wizard for deploying your own saasmail instance to Cloudflare. Use this skill when the user wants to set up saasmail, deploy it, configure Cloudflare resources, or get started with the project. Also trigger when the user says "onboarding", "setup", "deploy saasmail", "get started", or asks how to…
use-saasmail
Send transactional emails and enroll recipients in drip sequences through a deployed saasmail instance's HTTP API. Use this skill whenever the user wants to programmatically send mail, fire off a template, kick off an onboarding/drip sequence, manage recipient enrollment, or integrate their app with their self-hosted…