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 synaptiai/synapti-marketplace --skill repo-configgit clone --depth 1 https://github.com/synaptiai/synapti-marketplaceWrote 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/synaptiai/synapti-marketplace/repo-config)<a href="https://agentmods.dev/skills/synaptiai/synapti-marketplace/repo-config"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/repo-config/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/synaptiai/synapti-marketplace/repo-config"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/repo-config.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.00044 | $0.01014 |
| Opus 5 | $0.00022 | $0.00507 |
| Sonnet 5 | $0.00009 | $0.00203 |
| Haiku 4.5 | $0.00004 | $0.00101 |
Grade A, and why
repo-config 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 2d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Configuration
Reference skill loaded into agent context via skills: repo-config. Provides patterns for dynamic repository detection so agents never hardcode branch names, repo identifiers, or conventions.
Core Commands
Default Branch
Used by code-reviewer for diff base and convention-checker for commit range:
DEFAULT_BRANCH=$(gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name')
# Usage in agents:
git diff origin/$DEFAULT_BRANCH..HEAD # code-reviewer
git log --oneline $DEFAULT_BRANCH..HEAD # convention-checker
Repository Owner/Name
Used by implementation-planner for GitHub API calls:
REPO=$(gh repo view --json nameWithOwner --jq '.nameWithOwner')
# Usage in agents:
gh api repos/$REPO/issues/$ISSUE_NUMBER/comments
gh api repos/$REPO/pulls/$PR_NUMBER/comments
Combined Fetch
When multiple values are needed, minimize API calls:
gh repo view --json nameWithOwner,defaultBranchRef --jq '{
repo: .nameWithOwner,
default_branch: .defaultBranchRef.name
}'
Conventions
Used by convention-checker to validate branch names and commit messages. These defaults are configurable via settings.gh-workflow.json (see conventions.* keys in schema.json). Commands may also override with project-specific conventions from CLAUDE.md — check CLAUDE.md first, then settings, then these defaults.
Branch Naming
Configurable via .conventions.branchPatterns and .conventions.additionalBranchTypes in settings.
| Type | Default Pattern | Example |
|---|---|---|
| Feature | feature/issue-{N}-{desc} |
feature/issue-42-add-login |
| Fix | fix/issue-{N}-{desc} |
fix/issue-13-typo |
| Docs | docs/issue-{N}-{desc} |
docs/issue-7-readme |
Additional branch types can be added via .conventions.additionalBranchTypes (e.g., {"refactor": "refactor/issue-{N}-{desc}", "chore": "chore/issue-{N}-{desc}"}).
Commit Prefixes
Configurable via .conventions.commitTypes in settings.
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.
- 2d ago First seen · 113 lines · 44 tokens per session scan A d56149247749
repo-config is a skill published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed today), licensed Apache-2.0. It adds 44 tokens to every session and 1,014 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-09-10.
Other skills, from other repositories
document
Run /document pr | changelog | release-note | postmortem (or let it ask) to write the human facing prose about a change. Drafts from the real commits and diff, writing to the right place. Does not write code, tests, or specs.
create-pr
Creates a GitHub Pull Request on the current branch with a description focused on WHAT changed (not HOW). Uses emojis in the title and description. Use when the user asks to create a PR, open a pull request, or submit changes for review. Triggers on mentions of PR, pull request, merge request, or code review.
loop-close
Closes a slice or a session - adversarial audit of the diff, ledger entry, selective commit, honest report, and the handoff for the next session. Use before considering anything finished.
Implement
Implement one micro spec — one commit, one PR. The micro spec is the complete instruction set; write only the files in its File Operations table, verify against its acceptance criteria, commit.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
branch-and-worktree-workflow
Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting…