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/poindexter12/waypointWrote 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/poindexter12/waypoint/workflows)<a href="https://agentmods.dev/plugins/poindexter12/waypoint/workflows"><img src="https://agentmods.dev/badge/plugins/poindexter12/waypoint/workflows/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/poindexter12/waypoint/workflows"><img src="https://agentmods.dev/badge/plugins/poindexter12/waypoint/workflows.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
workflows 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
{
"name": "workflows",
"description": "Operational tooling for development workflows - git worktree management, GitHub issues backlog",
"version": "1.2.0",
"repository": "https://github.com/poindexter12/waypoint",
"license": "MIT",
"keywords": [
"git",
"worktree",
"workflow",
"branching",
"github",
"issues"
],
"agents": [
"./agents/consultant.md",
"./agents/gh-wrangler.md"
],
"commands": [
"./commands/adopt.md",
"./commands/destroy.md",
"./commands/list.md",
"./commands/new.md",
"./commands/status.md"
],
"skills": [
"./skills/working-tree",
"./skills/gh-issue-templates",
"./skills/gh-issue-triage",
"./skills/gh-issue-lifecycle"
]
}
What it installs
The manifest is a name and a version. 4 skills, 5 commands, 2 agents travel with it, and installing the plugin installs all of them — 390 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill gh-issue-lifecycle A 45 tokens
- Skill worktree-guide A 75 tokens
- Skill gh-issue-triage A 60 tokens
- Skill gh-issue-templates A 49 tokens
- Command adopt A 11 tokens
- Command destroy A 15 tokens
- Command list A 12 tokens
- Command status A 13 tokens
- Command new C 14 tokens
- Agent working-tree-consultant A 29 tokens
- Agent gh-wrangler B 67 tokens
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 · 33 lines scan A 5186951d08b0
workflows is a plugin published in the GitHub repository poindexter12/waypoint (7 stars, last pushed 9mo ago), 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
fuse-rules
Global rules for all Claude Code sessions: APEX workflow, SOLID/DRY enforcement, project detection, agent delegation, frontend/git standards.
lanes-bridges
Bridge Lanes with GitHub and Linear: import issues, batch-spawn a session per ticket, and post results back upstream. Split out of lanes-desktop in 0.7.0.
workbench
Ticket-to-PR development workflow: triage, plan with verified citations, implement inside the plan, review, commit, PR. Pluggable issue trackers (Jira, Azure DevOps, GitHub Issues) or a backlog in the repo, so it works with no tracker at all.
gh-cli
GitHub CLI integration with focused skills for pull requests, stacked pull requests, issues, GitHub Actions, and viewing GitHub file URLs.
tgc-skills
A shipping pipeline for Claude Code: orchestrate a locked plan with fresh-context agents, polish the diff, ship it to a reviewed PR, run an agent review-fix loop until clean, and clean up after merge.
github
Drive PRs to merge-ready with gh: fix CI and review-bot feedback, plus bulk merge, close, and label.