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/tartinerlabs/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/tartinerlabs/skills/workflow)<a href="https://agentmods.dev/plugins/tartinerlabs/skills/workflow"><img src="https://agentmods.dev/badge/plugins/tartinerlabs/skills/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/tartinerlabs/skills/workflow"><img src="https://agentmods.dev/badge/plugins/tartinerlabs/skills/workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
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 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.
What it actually says
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "workflow",
"displayName": "workflow",
"version": "2.0.0",
"description": "Git and GitHub workflow skills — commits, branches, pull requests, issues, and CI actions",
"author": {
"name": "Tartiner Labs",
"url": "https://github.com/tartinerlabs"
},
"homepage": "https://github.com/tartinerlabs/skills",
"repository": "https://github.com/tartinerlabs/skills",
"license": "MIT",
"keywords": [
"git",
"github",
"commit",
"branch",
"pull-request",
"issues",
"github-actions",
"ci"
],
"skills": "./skills/"
}
What it installs
The manifest is a name and a version. 6 skills travel with it, and installing the plugin installs all of them — 249 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 Changed e15e57d9b776
- 1mo ago First seen · 26 lines scan A 2bba3e255b0f
workflow is a plugin published in the GitHub repository tartinerlabs/skills (8 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-08-31.
Other plugins, from other repositories
ensemble-git
Git workflow automation and conventional commits.
cc-arsenal-git
Git and GitHub workflow skills: conventional commits, PR creation, release management, gitflow branching, branch syncing, and code-done-to-merged shipping.
utility-tools
Developer productivity tools for Claude Code — generate McKinsey-style HTML slide decks from marketing strategies, automate software releases with version bumping, changelog generation, git tagging, and GitHub release publishing. 3 skills for teams shipping fast.
git
Git workflow automation (commit, PR, branching, changelog).
jj
Jujutsu (jj) version control skills for committing, pushing, opening PRs, and rebasing.
pwdev-statusline
Configure and manage Claude Code status line — installs a rich, configurable bash status bar (single-jq-pass, dynamic colors, formatted tokens, truncated paths) showing model, git branch, context usage, rate limits, and token counts.