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.
git clone --depth 1 https://github.com/terrylica/cc-skillsWrote 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/plugins/terrylica/cc-skills/git-town-workflow)<a href="https://agentmods.dev/plugins/terrylica/cc-skills/git-town-workflow"><img src="https://agentmods.dev/badge/plugins/terrylica/cc-skills/git-town-workflow/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/plugins/terrylica/cc-skills/git-town-workflow"><img src="https://agentmods.dev/badge/plugins/terrylica/cc-skills/git-town-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
git-town-workflow 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 today.
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
{
"name": "git-town-workflow",
"description": "Prescriptive git-town workflow enforcement for fork-based development: fork creation, contribution workflow, enforcement hooks that block forbidden raw git commands",
"version": "34.5.1",
"source": "./plugins/git-town-workflow",
"category": "devops",
"author": {
"name": "terrylica",
"url": "https://github.com/terrylica"
},
"keywords": [
"git-town",
"fork",
"workflow",
"contribution",
"upstream",
"branch",
"prescriptive",
"hooks",
"enforcement"
],
"strict": false
}What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 59 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
2 files beside marketplace.json#git-town-workflow 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.
- today Changed abd64124d44e
- yesterday Changed 6b242f879df7
- 3d ago Changed 6be95baf7450
- 5d ago Changed cf6417135082
- 6d ago Changed b8e540da2e28
- 7d ago Changed dd41c6d61cfe
- 9d ago Changed 299bdfc6a4d4
- 10d ago Changed e0954fa3556b
- 12d ago Changed b89c9c44b1c8
- 17d ago First seen · 23 lines scan A f6d23fb0ca10
git-town-workflow is a plugin published in the GitHub repository terrylica/cc-skills (0 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-05.
Other plugins, from other repositories
commit-linter
Set up conventional commit linting.
dark-factory
Curie's default dark factory agent: one labelled GitHub issue in, one reviewed pull request or one stated reason out. One agent reads the issue through the platform's getissue tool, pins acceptance criteria, plans, gets the plan reviewed by an Opus plan-reviewer subagent, writes a failing test where feasible, implemen.
github-activity
Read-only GitHub activity reporter for program managers. One hosted connector reads merged pull requests, opened and closed issues, and milestone movement across several repositories since a point in time. It holds no write tool, the tool policy allows only the read tool so anything else fails closed, and the…
hydra
Git Worktree management for parallel agent execution - isolated working directories without Git conflicts.
git
Git workflow automation (commit, PR, branching, changelog).
create-pr
Streamlines pull request creation by handling the entire workflow: creating a new branch, committing changes, formatting modified files with Biome, and submitting the PR.