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 shikanime-labs/skills --skill sks-fastlanegit clone --depth 1 https://github.com/shikanime-labs/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/shikanime-labs/skills/sks-fastlane)<a href="https://agentmods.dev/skills/shikanime-labs/skills/sks-fastlane"><img src="https://agentmods.dev/badge/skills/shikanime-labs/skills/sks-fastlane/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/shikanime-labs/skills/sks-fastlane"><img src="https://agentmods.dev/badge/skills/shikanime-labs/skills/sks-fastlane.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.00037 | $0.01470 |
| Opus 5.5 | $0.00015 | $0.00588 |
| Sonnet 5.5 | $0.00007 | $0.00294 |
| Haiku 4.5 | $0.00004 | $0.00147 |
Grade A, and why
sks-fastlane 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 7d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fastlane Merge
Self-merge a trivial PR without human review. This is a mutator of
sks-land: it exists to state exactly which gates drop and which never
do. The full gate train (sks-pr-review → approval → sks-land) stays
the default; fastlane is the exception that must justify itself against
the eligibility gate, line by line.
For org-specific conventions (branch protection on main, the approval
fastlane replaces), read references/shikanime.md when operating in a
shikanime org.
When to Use
- "Fastlane this" / "merge it without review, it's trivial".
- A hotfix, small update, or insignificant chore the user does not want to sit through the review train for.
- Not for feature work, refactors, or anything the user did not frame
as trivial — that is
sks-pr+sks-land.
Eligibility gate (all must hold; any fail → full gates)
Run every check before merging. A False is not negotiable: route the
PR to sks-land and say which criterion failed.
-
Trivial framing. The change is a hotfix, small update, or insignificant chore. Feature work, refactors, and behavior changes beyond the minimal fix never fastlane.
-
Small diff. ≤5 files and ≤100 changed lines:
gh pr view <M> --repo <org>/<repo> --json files \ --jq '{files: (.files | length), lines: ([.files[].additions + .files[].deletions] | add)}' -
No trust boundary. No auth, secrets, credentials, network policy, IAM, TLS, or dependency-lock changes. A lockfile,
*.enc.*, or anything undersecrets/disqualifies regardless of diff size:gh pr view <M> --repo <org>/<repo> --json files \ --jq '.files[].path' | grep -Ei 'lock|secret|\.enc\.|auth|iam|cert|token' \ && echo DISQUALIFIED -
No schema, migration, or public API surface change.
-
CI green on the current head — a red or pending check never fastlanes:
gh pr checks <M> --repo <org>/<repo>
Procedure
- PR exists and is pushed. Fastlane merges; it does not build. No
PR yet means ship the unit first (
sks-delegate→sks-commit→sks-pr), then come back. - Run the eligibility gate. Any fail →
sks-land(full gates). - Keep the conventions gate (
sks-landGate 4): commit subject plain-English imperative, no conventional prefix, PR title equals the commit subject. Verify before merging:
What ships with it
3 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.
- 7d ago Changed 7424dea7bb2f
- 10d ago Changed 2015e229a250
- 17d ago Changed · +3 lines 70e0ba17e06c
- 19d ago Changed · +2 lines 6922f36f6253
- 24d ago First seen · 148 lines · 37 tokens per session scan A 93c08baaf5d6
sks-fastlane is a skill published in the GitHub repository shikanime-labs/skills (2 stars, last pushed today), licensed Apache-2.0. It adds 37 tokens to every session and 1,470 once invoked, about $0.0001 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-09-25.
Other skills, from other repositories
git-conventional-commits
Author standardized conventional commit messages (feat, fix, docs, refactor, chore), generate automated semver releases, and format pull request descriptions.
git-workflow-and-versioning
Git workflow and versioning practices. Use when committing, branching, resolving conflicts, organizing work across multiple parallel streams, cutting a release, choosing a semantic version bump, tagging, or writing a changelog.
auto-commit
Autonomously group, stage, and commit repository changes into atomic commits.
oss-forensics
Supply chain investigation, evidence recovery, and forensic analysis for GitHub repositories. Covers deleted commit recovery, force-push detection, IOC extraction, multi-source evidence collection, hypothesis formation/validation, and structured forensic reporting. Inspired by RAPTOR's 1800+ line OSS Forensics system.
github-pr-workflow
GitHub PR lifecycle: branch, commit, open, CI, merge.
github-pr-workflow
GitHub PR lifecycle: branch, commit, open, CI, merge.