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 gyanranjan/polyagent-skills --skill repo-bootstrapgit clone --depth 1 https://github.com/gyanranjan/polyagent-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/gyanranjan/polyagent-skills/repo-bootstrap)<a href="https://agentmods.dev/skills/gyanranjan/polyagent-skills/repo-bootstrap"><img src="https://agentmods.dev/badge/skills/gyanranjan/polyagent-skills/repo-bootstrap/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/gyanranjan/polyagent-skills/repo-bootstrap"><img src="https://agentmods.dev/badge/skills/gyanranjan/polyagent-skills/repo-bootstrap.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.00066 | $0.00751 |
| Opus 5 | $0.00033 | $0.00376 |
| Sonnet 5 | $0.00013 | $0.00150 |
| Haiku 4.5 | $0.00007 | $0.00075 |
Grade A, and why
repo-bootstrap 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 10d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo Bootstrap
Purpose
Create well-structured, production-ready project scaffolds with appropriate tooling, CI/CD, documentation, and conventions for any tech stack.
When to Use
- User asks to set up a new project or repository
- User wants a scaffold for a specific tech stack
- User needs best-practice project structure
When NOT to Use
- User needs improvements to an existing repository without scaffolding from scratch
- User only wants one isolated file template and no broader project setup
Inputs
Required:
- Project type — what's being built (API, web app, CLI tool, library, etc.)
- Tech stack — language/framework preferences
Optional:
- Team size and conventions
- CI/CD platform preference (GitHub Actions, GitLab CI, etc.)
- Deployment target (AWS, GCP, Vercel, etc.)
Process
Step 1: Gather Requirements
Understand the project type, stack, and any organizational conventions.
Step 2: Design Structure
Plan the directory layout following the stack's conventions and best practices.
Step 3: Validate Design Readiness (Before Scaffolding)
Apply common-skills/design-readiness-gate.md for language, database, architecture pattern, and logging/observability baseline decisions.
If key decisions are open, scaffold only requirement/spec structure and block coding scaffold tasks in agent.todo.md.
Step 4: Generate Files
Create all scaffold files including: README, LICENSE, .gitignore, CI config, linting config, folder structure, and starter code.
Step 5: Add Documentation
Include README with setup instructions, CONTRIBUTING guide, and architecture notes.
Step 6: Validate
Run linters and build tools to ensure the scaffold is immediately usable.
Output Format
Complete directory structure with all files. Ready to git init and push.
Quality Checks
- Generated structure matches the requested language/framework conventions
- Setup commands in README are runnable on a clean machine
- CI, linting, and formatting configs are present and coherent
- No placeholder values remain in generated docs or configs
- Pre-coding design readiness decisions are recorded or unresolved items are explicitly blocked
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.
- 10d ago First seen · 88 lines · 66 tokens per session scan A cabc13e6f957
repo-bootstrap is a skill published in the GitHub repository gyanranjan/polyagent-skills (2 stars, last pushed 6mo ago), licensed MIT. It adds 66 tokens to every session and 751 once invoked, about $0.0003 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
gh-bootstrap
Initialize GitHub repository configuration from vetted upstream templates. Use when setting up repository automation, issue and PR templates, CI workflows, or baseline GitHub project files for a new or existing repo.
mk:bootstrap
Use when creating a new project from scratch — orchestrates the full journey from idea to running code. Research → design → plan → scaffold → implement → docs. Explicit invocation only — never auto-activates. CLI = project infrastructure (.claude/), bootstrap = application code + full pipeline. NOT for autonomous…
repo-bootstrap
Automate full ANAMIZED product repo structure (Server OS parity) including USDC, Stripe, badges, CI, skills, AGENTS.md.
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…