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.
npx skills add dryvist/claude-code-plugins --skill shared-workflow-org-refsgit clone --depth 1 https://github.com/dryvist/claude-code-pluginsWrote 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/dryvist/claude-code-plugins/shared-workflow-org-refs)<a href="https://agentmods.dev/skills/dryvist/claude-code-plugins/shared-workflow-org-refs"><img src="https://agentmods.dev/badge/skills/dryvist/claude-code-plugins/shared-workflow-org-refs/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/dryvist/claude-code-plugins/shared-workflow-org-refs"><img src="https://agentmods.dev/badge/skills/dryvist/claude-code-plugins/shared-workflow-org-refs.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.00053 | $0.00811 |
| Opus 5 | $0.00026 | $0.00405 |
| Sonnet 5 | $0.00011 | $0.00162 |
| Haiku 4.5 | $0.00005 | $0.00081 |
Grade A, and why
shared-workflow-org-refs 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 8d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shared Workflow Org References
GitHub Actions reusable-workflow and action uses: clauses are the one place the
"don't rewrite JacobPEvans/* on sight — the redirect holds" rule does NOT apply.
Two hard GitHub constraints:
uses:cannot contain expressions or variables — the owner is always a literal.uses: ${{ vars.X }}/repo/...@refis rejected. No org variable can centralize it.uses:does NOT follow repository transfer/rename redirects (by design). API, git, and the browser DO follow them; Actions does not.
Consequence: when a shared-CI repo changes orgs, every consumer's uses: fails at parse time
(the run shows zero jobs and "workflow was not found"). There is no runtime variable that prevents this.
Canonical home: dryvist
dryvist is the canonical home for everything dryvist uses. Anything a dryvist
repo consumes — reusable workflows, presets, policies — belongs under dryvist/*.
JacobPEvans-personal/* may depend on dryvist/*; dryvist/* must never depend
on JacobPEvans-personal/*. When a shared workflow is used by dryvist, its home is
dryvist/.github (or the relevant dryvist/* repo), not the personal account.
Because uses: does not follow redirects, reference each workflow by its literal
current owner from the table below until a pending relocation actually lands.
| Shared-CI workflow set | Current home | Status |
|---|---|---|
ai-workflows reusable workflows |
dryvist/ai-workflows |
canonical |
Nix reusable workflows (_nix-validate.yml, _nix-build.yml) |
dryvist/.github |
canonical |
Release-please (_release-please.yml) |
dryvist/.github |
canonical — org-native (dryvist release App, major-bump block, auto-merge) |
_markdown-lint, _file-size, _osv-scan, _ci-gate, … |
JacobPEvans-personal/.github |
pending relocation to dryvist/.github |
Nix and release-please were deliberately relocated to dryvist/.github (the org owns
its own CI). The remaining non-Nix .github workflows are still in
JacobPEvans-personal/.github only until they are moved the same way — that is a
transitional home, not a permanent one. Repoint consumers via the sweep below as each
moves; do not move any back to the personal account.
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.
- 8d ago First seen · 56 lines · 53 tokens per session scan A 8c34ed32ebfb
shared-workflow-org-refs is a skill published in the GitHub repository dryvist/claude-code-plugins (3 stars, last pushed today), licensed Apache-2.0. It adds 53 tokens to every session and 811 once invoked, about $0.0003 per session on Opus 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-04.
Other skills, from other repositories
github-release-management
GitHub release orchestration — automated versioning, testing, deployment, and rollback. Use when cutting a release, tagging a version, drafting release notes, or coordinating a deploy/rollback workflow.
ci-cd-pipeline-patterns
Comprehensive CI/CD pipeline patterns skill covering GitHub Actions, workflows, automation, testing, deployment strategies, and release management for modern software delivery.
autonomous-pr
Otonom PR yasam dongusu. PR olustur, CI bekle, hata varsa duzelt, review feedback'i uygula, merge'e hazirla. Budget ve zaman limiti ile kontrol altinda tutulan tam otonom PR pipeline'i.
research-archival
Scrape AI research URLs, archive with frontmatter, create GitHub Issues with identity verification.
issues-workflow
Plan and track work using a GitHub Issues-first workflow with sub-issue hierarchies, issue-branch-PR lifecycle, and auto-close on merge.
worktree-manager
Create alpha-forge git worktrees with auto branch naming. TRIGGERS - create worktree, new worktree, alpha-forge worktree.