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 agentmods add skills/firatcand/forge/setup-reponpx skills add firatcand/forge --skill setup-repogit clone --depth 1 https://github.com/firatcand/forgeWrote 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/firatcand/forge/setup-repo)<a href="https://agentmods.dev/skills/firatcand/forge/setup-repo"><img src="https://agentmods.dev/badge/skills/firatcand/forge/setup-repo.svg" alt="Measured on agentmods" 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.00031 | $0.00484 |
| Opus 5 | $0.00015 | $0.00242 |
| Sonnet 5 | $0.00006 | $0.00097 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
setup-repo 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 6d 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
/setup-repo
Delegate to the devops-engineer subagent.
Preconditions
ghCLI installed and authenticated- spec/PRD.md exists
- Run from inside the project directory
Steps (transparent — show each to user, don't hide)
- Verify gh CLI:
gh auth status - Create repo:
gh repo create [name] --private --source=. --remote=origin- Or skip if origin already exists
- Initial commit: if no commits, commit current state to
main - Branch protection on main:
- Require PR review (1)
- Require
teststatus check - No direct pushes
- No force pushes
- GitHub Environments:
development(auto-deploy, no approval)production(manual approval)
- Copy CI workflows from
templates/github-workflows/to.github/workflows/:claude-issue.ymlclaude-pr-review.ymltest.ymlclaude-scheduled.yml
- Generate
.env.examplefrom SPEC.md env_vars list - Setup Claude Code OAuth token:
- Prompt user:
claude setup-token - Read token from clipboard or stdin
- Set as repo secret:
gh secret set CLAUDE_CODE_OAUTH_TOKEN
- Prompt user:
- Commit and push:
.github/, updated.env.example
Each step shown to user
Don't run all 9 steps silently. Print each:
[1/9] Verifying gh CLI authentication... ✓
[2/9] Creating repo firatcand/time-logger... ✓
[3/9] Initial commit on main... ✓
...
User can interrupt at any step.
Output
Repo URL + summary of what was configured. Branch protection rules summary. Workflow files list.
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.
- 6d ago First seen · 60 lines · 31 tokens per session scan A 2d1df729027e
setup-repo is a skill published in the GitHub repository firatcand/forge (13 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 484 once invoked, about $0.0002 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-30.
Other skills, from other repositories
release
Generic release assistant — analyzes repo release rules, caches them in .omc/RELEASERULE.md, then guides the release.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
ci-pipeline
Push current branch and return the pipeline tracking URL (GitLab or GitHub Actions).
shared-tooling-git-hooks
Husky v9 setup, lint-staged v16 patterns, commitlint with conventional commits, CI/production handling, monorepo setup, migration from v8.
release
Cut a prospec GitHub release — bump version strings, tag, and publish release notes in the established format so the Release Binaries workflow attaches multi-platform binaries. Triggers: release, publish release, cut a release, ship a version, 發布, 發佈, 出版本, 發版, 版本發布, 發布 release.
submit-pr
Open a prospec pull request in the house format — push the change's two commits, write the Traditional Chinese body, and link it to its issue. Triggers: submit pr, open pr, 開 PR, 送 PR, 發 PR, pull request, 提交 PR.