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 slamb2k/mad-skills --skill start-rightgit clone --depth 1 https://github.com/slamb2k/mad-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/slamb2k/mad-skills/start-right)<a href="https://agentmods.dev/skills/slamb2k/mad-skills/start-right"><img src="https://agentmods.dev/badge/skills/slamb2k/mad-skills/start-right/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/slamb2k/mad-skills/start-right"><img src="https://agentmods.dev/badge/skills/slamb2k/mad-skills/start-right.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00175 | $0.02998 |
| Opus 5 | $0.00088 | $0.01499 |
| Sonnet 5 | $0.00035 | $0.00600 |
| Haiku 4.5 | $0.00017 | $0.00300 |
Grade A, and why
start-right 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 9d 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 — 377 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Start Right
Complete repository initialization and scaffolding for new projects with production-ready CI/CD workflows, validation checks, and automated releases.
Overview
This skill provides end-to-end repository setup for solo developers, automating everything from git initialization to production deployment workflows. It handles project type detection, appropriate tooling configuration, GitHub repository creation, branch protection, validation checks, git hooks, and comprehensive GitHub Actions workflows.
Workflow Decision Tree
When a user requests repo initialization/scaffolding:
- Determine project type → Detect or ask user for project type (node/typescript/react/rust/python/go/docker/skill)
- Gather preferences → Ask about:
- Repository visibility (public/private)
- Organization (if applicable)
- Validation checks to enable (format, lint, type-check, test, build, integration-test)
- Git hooks preference (husky for Node.js projects, lefthook for others)
- Release strategy (npm, github-pages, vercel, docker, binary, pypi, crates.io, skill)
- Execute scaffolding → Run setup scripts in order
- Verify and report → Confirm all components are configured correctly
Scaffolding Process
Step 1: Prerequisites Check
Before starting, verify:
- Git is installed
- GitHub CLI (gh) is installed and authenticated
- Current directory is the intended project location
- Directory is empty or contains minimal files
# Check prerequisites
git --version
gh --version
gh auth status
If prerequisites are missing, provide installation instructions:
- Git:
brew install git(macOS) or system package manager - GitHub CLI:
brew install ghor from https://cli.github.com - Authentication:
gh auth login
Step 2: Git Initialization
Initialize git repository with main as default branch:
python3 scripts/init_git_repo.py <repo-name> [--private] [--org <org>] [--type <project-type>]
Options:
--private: Create private repository (default: public)--org <n>: Create under organization--type <type>: Project type for appropriate .gitignore (node, python, rust, go)
What ships with it
7 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.
- references/project-types.md 5.8 KB
- references/release-strategies.md 8.7 KB
- scripts/generate_workflows.py 18 KB runs code
- scripts/init_git_repo.py 5.4 KB runs code
- scripts/setup_branch_protection.py 4.1 KB runs code
- scripts/setup_git_hooks.py 8.6 KB runs code
- scripts/setup_tooling.py 5.8 KB runs code
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.
- 9d ago First seen · 377 lines · 175 tokens per session scan A cbd61836d221
start-right is a skill published in the GitHub repository slamb2k/mad-skills (5 stars, last pushed 3d ago), licensed MIT. It adds 175 tokens to every session and 2,998 once invoked, about $0.0009 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-31.
Other skills, from other repositories
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. (gstack).
releasepr
Adopt, configure, run, or troubleshoot compozy/releasepr in a consuming repository, including Actions, beta/stable/legacy plans, notes, dry-runs, and publication. Excludes pr-release internals and general versioning advice.
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…
seed-snapshot-release
An automated workflow for creating and tracking a snapshot release of the pull request on the current branch. A snapshot release is a temporary package build used for testing a branch before a normal release.
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
release-engineering
Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness. Use when preparing a release, shipping a risky PR, coordinating app/backend/database rollout, recovering from a bad deploy, or defining release…