agentic-stack is a portable layer of agent memory, skills, and protocols stored in a .agent/ folder that can be used across multiple coding-agent tools. It is for people who switch between agent harnesses while keeping shared knowledge and monitoring data. The catalogue entries provide skills and rules for this shared agent layer.
Borrowing it
Nothing to install: this file belongs to codejunkie99/agentic-stack. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/codejunkie99/agentic-stack/master/.agent/skills/git-proxy/SKILL.mdgit clone --depth 1 https://github.com/codejunkie99/agentic-stackWrote 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/codejunkie99/agentic-stack/git-proxy)<a href="https://agentmods.dev/skills/codejunkie99/agentic-stack/git-proxy"><img src="https://agentmods.dev/badge/skills/codejunkie99/agentic-stack/git-proxy/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/codejunkie99/agentic-stack/git-proxy"><img src="https://agentmods.dev/badge/skills/codejunkie99/agentic-stack/git-proxy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Rogue Agent · line 32 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
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.00003 | $0.00360 |
| Opus 5.5 | $0.00001 | $0.00144 |
| Sonnet 5.5 | $0.00001 | $0.00072 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
git-proxy 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 1mo 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
Git Proxy — all git operations with a safety net
Handle git operations consistently. The fences (constraints above) are
enforced by the pre_tool_call hook; this file tells the agent what good
behavior looks like within those fences.
Commit
- Stage specific files, not
git add -A(avoids capturing secrets). - Write messages that explain why, not what.
- Reference the task or issue if one exists.
Push
- Run tests first. If tests aren't present, say so explicitly.
- Never force-push to a protected branch. The pre-call hook will block this even if you try.
- Prefer
--force-with-leaseover--forceon feature branches.
Branch / merge / rebase
- Rebase feature branches on
mainbefore opening a PR. - Resolve conflicts manually; do not
-X theirsor-X ourswithout thinking. - Merge via PR with review, not directly on the command line.
Self-rewrite hook
After every 5 uses, re-read KNOWLEDGE.md and the last 10 git-proxy
episodic entries. If a new failure mode has appeared, append a heuristic
to KNOWLEDGE.md. If a constraint was violated, escalate to LESSONS.md.
What ships with it
1 file 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.
- 1mo ago First seen · 36 lines · 3 tokens per session scan A a36a77360096
git-proxy is a skill published in the GitHub repository codejunkie99/agentic-stack (2,302 stars, last pushed 9d ago), licensed Apache-2.0. It adds 3 tokens to every session and 360 once invoked, about $0.0000 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-08-30.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.