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 ivanhoinacki/team-exp-claude-config --skill create-prgit clone --depth 1 https://github.com/ivanhoinacki/team-exp-claude-configWrote 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/ivanhoinacki/team-exp-claude-config/create-pr)<a href="https://agentmods.dev/skills/ivanhoinacki/team-exp-claude-config/create-pr"><img src="https://agentmods.dev/badge/skills/ivanhoinacki/team-exp-claude-config/create-pr/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/ivanhoinacki/team-exp-claude-config/create-pr"><img src="https://agentmods.dev/badge/skills/ivanhoinacki/team-exp-claude-config/create-pr.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.00039 | $0.04931 |
| Opus 5 | $0.00019 | $0.02465 |
| Sonnet 5 | $0.00008 | $0.00986 |
| Haiku 4.5 | $0.00004 | $0.00493 |
Grade A, and why
create-pr 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 — 412 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Pull Request
References
| File | Content |
|---|---|
| references/pr-template.md | PR body template, content generation guide, diagram pipeline |
| references/ci-monitor.md | Background CI agent: polling, auto-fix logic, escalation rules |
| references/learnings.md | Lessons from past PR sessions (review before each PR) |
Working Directories
- Obsidian workspace (docs, plans, features):
__VAULT_ROOT__ - Codebase (all LE services):
__CODEBASE_ROOT__
Pre-checks
-
Verify not on
mainorprod. If so, create a feature branch first. -
Check for uncommitted work, commit first if needed.
-
Verify Manual-E2E-Recipe exists (mandatory, blocks PR creation):
VAULT="__VAULT_ROOT__" TICKET=$(git branch --show-current | grep -oE 'EXP-[0-9]+|BUG007-[0-9]+' | head -1) RECIPE=$(find "$VAULT/Development/Features" -maxdepth 3 -name "Manual-E2E-Recipe.md" -path "*${TICKET}*" 2>/dev/null | head -1) [ -n "$RECIPE" ] && echo "E2E Recipe: $RECIPE" || echo "WARN: No Manual-E2E-Recipe.md found for $TICKET"If missing: run
/test-scenariosfirst (Phase 5 creates the recipe). Do NOT proceed without it. If the feature is docs-only or config-only (no testable behavior), skip with note "N/A: config-only change". -
Run CI checks locally (mandatory, blocks PR creation): If
/code-reviewalready ran CI checks in this session AND all passed, skip this step (checks already validated). Otherwise, run the shared CI check script:~/.claude/scripts/ci-local-check.sh .This auto-detects
package.jsonscripts and runs lint, types, build, and tests in order.If ANY check fails: fix the issue, commit the fix, then retry. Do NOT proceed to PR creation with failing checks.
-
Read the full diff:
GIT_EDITOR=true git diff main...HEAD -
Read all changed files completely (not just the diff) to understand context.
-
Prepend
GIT_EDITOR=trueto all git commands.
What ships with it
2 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.
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 · 412 lines · 39 tokens per session scan A beb23bb49ceb
create-pr is a skill published in the GitHub repository ivanhoinacki/team-exp-claude-config (2 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 4,931 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-31.
Other skills, from other repositories
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
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.
chinese-commit-conventions
A Chinese-language guide to Conventional Commits, a format for writing consistent Git commit messages, plus related changelog, commit-checking, and commit-helper configuration.
managing-git
Manages Git workflows including branching, commits, and pull requests. Use when working with Git, creating commits, opening PRs, managing branches, resolving conflicts, or when asked about version control best practices.
updater_guide
Guidance for checking for and installing Row-Bot updates.