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 psenger/ai-agent-skills --skill startgit clone --depth 1 https://github.com/psenger/ai-agent-skillsWrote 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/psenger/ai-agent-skills/start)<a href="https://agentmods.dev/skills/psenger/ai-agent-skills/start"><img src="https://agentmods.dev/badge/skills/psenger/ai-agent-skills/start/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/psenger/ai-agent-skills/start"><img src="https://agentmods.dev/badge/skills/psenger/ai-agent-skills/start.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.00154 | $0.00996 |
| Opus 5.5 | $0.00062 | $0.00398 |
| Sonnet 5.5 | $0.00031 | $0.00199 |
| Haiku 4.5 | $0.00015 | $0.00100 |
Grade A, and why
start 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 1mo 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Start
Begins a new piece of work. Two modes — the skill determines which applies:
- User provides an issue number, URL, or reference → EXISTING ISSUE mode
- User provides a description of what needs doing → NEW ISSUE mode
For branch naming and commit format, follow the conventions skill.
Step 0 — Auth & Identity
Check for a GitHub MCP server in available tools. If none, run:
gh auth status
If neither is available, stop: "I need the GitHub MCP server or gh CLI authenticated to continue. Run gh auth login or connect the GitHub MCP server."
Confirm identity — use mcp__github__get_me if the GitHub MCP server is available, otherwise:
gh api user --jq '"@\(.login) — \(.name)"'
Show the result and ask: "I'll be acting as @username — is that right?" Wait for confirmation before continuing.
EXISTING ISSUE Mode
Step 1 — Fetch the Issue
From the issue number or URL, fetch the issue:
gh issue view <number> --json number,title,body,labels,url
Display the issue number, title, and first few lines of the body. Ask: "Is this the right issue to work on?" Wait for confirmation.
Step 2 — Start from Main
git checkout main
git pull origin main
git status --porcelain # must be empty — abort if dirty
Step 3 — Cut the Branch
Derive the slug from the issue title: lowercase, hyphenated, 2–4 meaningful words, no stop words.
Determine branch prefix from issue labels:
buglabel →fix/enhancementorfeaturelabel →feature/- Anything else →
feature/by default
git checkout -b <prefix><issue-number>-<slug>
Example: feature/14-add-handoff-skill or fix/23-vault-scribe-toc
Report: "Branch feature/14-add-handoff-skill created from main. You're ready to work."
NEW ISSUE Mode
Step 1 — Classify the Work
From the user's description, determine: is this a feature (new capability, new skill, enhancement) or a bug (something broken, incorrect behaviour, wrong output)?
What ships with it
4 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.
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.
- 1mo ago First seen · 111 lines · 154 tokens per session scan A 26a70640a91a
start is a skill published in the GitHub repository psenger/ai-agent-skills (14 stars, last pushed 5mo ago), licensed MIT. It adds 154 tokens to every session and 996 once invoked, about $0.0006 per session on Opus 5.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
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…