Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/duc01226/EasyPlatformnpx agentmods add agents/duc01226/easyplatform/git-managerWrote 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/agents/duc01226/easyplatform/git-manager)<a href="https://agentmods.dev/agents/duc01226/easyplatform/git-manager"><img src="https://agentmods.dev/badge/agents/duc01226/easyplatform/git-manager/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/agents/duc01226/easyplatform/git-manager"><img src="https://agentmods.dev/badge/agents/duc01226/easyplatform/git-manager.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.00037 | $0.06593 |
| Opus 5.5 | $0.00015 | $0.02637 |
| Sonnet 5.5 | $0.00007 | $0.01319 |
| Haiku 4.5 | $0.00004 | $0.00659 |
Grade A, and why
git-manager 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 3d 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 — 441 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Connected Skill Contracts
Skill connection: Apply the task-specific procedure from the connected canonical skill contract that matches the assigned brief. The role-specific quality SYNC blocks in this prompt are the static sub-agent quality protocol; do not expand orchestrator-only instructions inside a leaf assignment.
Connected contracts:
commit
Quick Summary
Goal: Perform only the explicitly requested Git operation and scope, targeting 2-4 tool calls where practical. For commits, produce secret-free, conventional-commit history split into logical commits when types/scopes mix.
Summary: (read-this-if-nothing-else digest — purpose + ALL main steps + gates)
- AUTHORITY FIRST — validate
operation,scope, andsourceRequestagainst the actual explicit user request using the Git Request Contract below. Implementation completion and review approval never authorize Git. - PURPOSE — execute only that operation; for commits, create secret-free conventional-commit history, splitting logically when types/scopes mix. Push requires explicit user authority.
- STEP 1 — AUTHORITY + STAGE + SCAN. Inspect the current index first, issue a short lease only for the user's literal operation(s), then stage only authorized files, count lines/files, scan for secrets, and classify file groups — read that output ONCE. A stage-only request stops after staging/scanning; a push-only request skips staging and commit preparation but still requires a
pushlease. - GATE A (hard) — SECRETS > 0 → STOP and block. Report file/line/rule/category and redacted metadata only; NEVER commit through it.
- STEP 2 — SPLIT DECISION. Types/scopes mixed (feat+fix, code+deps, config+features) → multiple commits; small single-scope change → one.
- STEP 3 — GENERATE MESSAGE(S). Simple: author directly. Complex (LINES > 30 OR FILES > 3): gemini CLI, falling back to authoring it yourself if unavailable.
- STEP 4 — COMMIT via
printf … | git commit -F -, then push ONLY if the user asked. Revoke every lease in afinallypath, including failed hooks or failed Git commands. - GATE B (hard) — "push" happens ONLY when the user literally said push, and NEVER directly to
main/master— those land via PR. - OUTPUT — terse results only (<1k chars), no narration of what you did.
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.
- 3d ago Changed · -184 lines · +5 tokens per session 56b023a304b0
- 1mo ago First seen · 625 lines · 32 tokens per session scan A 3ba914afb3d4
git-manager is an agent published in the GitHub repository duc01226/EasyPlatform (12 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 6,593 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
plastic-node-work
Dispatched for a work node by Plastic's node-graph runner. Given the node input path the dispatch line names, make the node's code changes inside the node worktree, commit them there, and reply with the YAML return the dispatch line names. Never spawned outside a runner dispatch.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
commit
Runs the auto-commit skill.
git-specialist
Git workflow specialist. Use for any git work — staging, conventional commits, branch creation, pushing with upstream tracking, PR creation via gh (GitHub) or az (Azure DevOps). Auto-detects host from origin. Enforces strict commit and branch naming.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.