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 urmzd/dotfiles --skill repo-initgit clone --depth 1 https://github.com/urmzd/dotfilesWrote 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/urmzd/dotfiles/repo-init)<a href="https://agentmods.dev/skills/urmzd/dotfiles/repo-init"><img src="https://agentmods.dev/badge/skills/urmzd/dotfiles/repo-init/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/urmzd/dotfiles/repo-init"><img src="https://agentmods.dev/badge/skills/urmzd/dotfiles/repo-init.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.00107 | $0.00752 |
| Opus 5.5 | $0.00043 | $0.00301 |
| Sonnet 5.5 | $0.00021 | $0.00150 |
| Haiku 4.5 | $0.00011 | $0.00075 |
Grade A, and why
repo-init 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.
What it actually says
Repo Init
Bootstrap a complete repository from zero to pushed.
Steps
-
Create GitHub repo:
gh repo create <name> --<visibility> --description "<description>" --clone(default public). -
Add LICENSE: Create an Apache-2.0 LICENSE file in the repo root.
-
Scaffold: If a language is specified, invoke
scaffold-project(which dispatches toscaffold-<lang>) to produce:- CI workflow (
.github/workflows/ci.yml) and release workflow (.github/workflows/release.yml); seesetup-ci. sr.yamlfor semantic release; seesync-release.- Task runner native to the language (npm scripts, Makefile, cargo, justfile for Python).
.envrcvia thesetup-devenvdirenv pattern (vanilla direnv + per-language version manager, not a Nix dev shell).- Language-specific config (Cargo.toml, go.mod, pyproject.toml, package.json, etc.).
- CI workflow (
-
Community health: Invoke
community-healthto addCODE_OF_CONDUCT.md,SECURITY.md,.github/pull_request_template.md, and.github/ISSUE_TEMPLATE/(bug report, feature request, config). Substitute{OWNER},{REPO},{CURRENT_MAJOR}, and{CHECK_COMMAND}placeholders. For a brand-new pre-1.0 project, set{CURRENT_MAJOR}to0and rewrite the SECURITY.md supported-versions table to0.x Yes / < 0.x No. -
README: Generate a README with the repo name, description, and standard badge layout.
-
Set metadata:
gh repo edit --add-topic <topics> --description "<description>"with relevant topics for the language/type. -
Initial commit and push:
git add -A(safe here since it's a brand new repo)git commit -m "chore: initial project scaffold"git push -u origin main
-
Report: Show the repo URL.
Rules
- Default to Apache-2.0 license.
- Default to public visibility.
- If no language is specified, create a minimal repo with just LICENSE, README, and .gitignore.
- Use conventional commits for the initial commit.
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 · 63 lines · 107 tokens per session scan A f38dc1185d37
repo-init is a skill published in the GitHub repository urmzd/dotfiles (5 stars, last pushed today), licensed Apache-2.0. It adds 107 tokens to every session and 752 once invoked, about $0.0004 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
use-codefresh
Reference for using Codefresh via the CodeFresh CLI (run from its Docker image). Use when a Codefresh CI check is failing in a recursionpharma PR, or when working with Codefresh builds.
scan-commit
Automatically scan the repository for unstaged/untracked changes, group them into logical commits using hunk-level analysis, stage and commit them following Conventional Commits.
smart-commit
Analyze staged changes and split them into multiple logical commits following Conventional Commits.
create-pr
Rebase from the latest origin/main, squash the commits from it, and then create a PR on github with intelligent commit messages based on staged changes.
pr-review
Intelligent PR code review with dynamic agent allocation based on change types. Analyzes PR changes and generates targeted review tasks.
analyze-pr
Analyze a GitHub/GitLab Pull Request by fetching its diff, reading its web description, and generating a comprehensive document. Use when the user provides a PR link and wants to understand what changes the PR introduces, or asks to review/analyze/summarize a pull request.