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 jrjsmrtn/project-orchestration-skills --skill harden-github-actionsgit clone --depth 1 https://github.com/jrjsmrtn/project-orchestration-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/skills/jrjsmrtn/project-orchestration-skills/harden-github-actions)<a href="https://agentmods.dev/skills/jrjsmrtn/project-orchestration-skills/harden-github-actions"><img src="https://agentmods.dev/badge/skills/jrjsmrtn/project-orchestration-skills/harden-github-actions/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/jrjsmrtn/project-orchestration-skills/harden-github-actions"><img src="https://agentmods.dev/badge/skills/jrjsmrtn/project-orchestration-skills/harden-github-actions.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.00101 | $0.04135 |
| Opus 5 | $0.00051 | $0.02067 |
| Sonnet 5 | $0.00020 | $0.00827 |
| Haiku 4.5 | $0.00010 | $0.00413 |
Grade B, and why
harden-github-actions scanned grade B with 2 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 12d 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.
Downloads and executes remote codemediumSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
A CI job runs third-party code (actions, installed tools) with a `GITHUB_TOKEN` and often OIDC. A mutable action tag (`@v4`) can be repointed to malicious code; an over-privileged token can push commits, publish packages Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
A CI job runs third-party code (actions, installed tools) with a `GITHUB_TOKEN` and often OIDC. A mutable action tag (`@v4`) can be repointed to malicious code; an over-privileged token can push commits, publish packages How it starts
The opening of the file, as written. The whole thing — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harden GitHub Actions
Harden GitHub Actions CI/CD workflows against supply-chain attack: pin what runs, minimise what it can do, and verify what it fetches.
GitHub-specific by design. Unlike most orchestration skills, this one is deliberately bound to one forge. The hardening controls below are not portable concepts wearing GitHub syntax — they are properties of the GitHub Actions execution model itself: third-party actions resolved by mutable git ref, an ambient
GITHUB_TOKENwith repository-wide default scopes, and OIDC-backed SLSA provenance. It has a sibling,harden-gitlab-ci, which is not a translation of this skill: GitLab's risks sit in different places (include:/CI-Catalog components, and aCI_JOB_TOKENthat defaults to own-project-only — so there the work is keeping it scoped, the opposite posture from here). Forgejo Actions is Actions-compatible in shape but resolves actions against its instance's configured registry, so pinning guidance does not transfer unchanged (roadmap H9).
When to Use
- When adding GitHub Actions workflows to a project (after
setup-git-hooks) - When auditing existing
.github/workflows/before making a repository public - When a supply-chain review (or the
supply-chainskill) flags CI hardening gaps - When standardising CI hardening across GitHub projects
Not for: GitLab CI — use harden-gitlab-ci. Not for Forgejo/Gitea Actions — the controls do not carry over unchanged. Say so rather than approximating.
This skill hardens CI workflows. validate-quality-config only reads CI to confirm parity with local hooks — it does not check pinning, permissions, or provenance. The two are complementary.
Required Inputs
- Workflow files — the project's
.github/workflows/*.yml - Release model — does the project publish artifacts/images/packages (needs provenance + signing), or is it internal-only?
- Repository visibility — public or private (affects Scorecard
publish_resultsand OSSF publishing)
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.
- 12d ago First seen · 306 lines · 101 tokens per session scan B 55e48c331b47
harden-github-actions is a skill published in the GitHub repository jrjsmrtn/project-orchestration-skills (15 stars, last pushed 8d ago), licensed MIT. It adds 101 tokens to every session and 4,135 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
turborepo
Turborepo monorepo build-system guidance — turbo.json task pipelines, caching, the turbo CLI, --filter/--affected, CI, env vars, and packages. Use when configuring tasks, sharing code between apps, or debugging the cache.
ci-routing
The canonical route-on-verdict protocol for a red CI diagnosis — fixable/flake/infra/needs-debug handling, the single-render rule, and the fix-then-re-watch loop. Use after orc-ci-investigator returns; /orc:ci Phase 3 and /orc:flow's post-open CI gate delegate here.
setup
Guided onboarding for nullius in this repo — detects test frameworks to propose Oracle config, offers the GitHub Action CI check, and walks through enabling the hook plugin. Use when a user asks to set up, install, enable, configure, or onboard nullius, or asks what nullius needs to be fully working here.
cpv-publish-to-marketplace
Use when publishing a plugin to a GitHub-hosted marketplace. Used dynamically via cpv-the-skills-menu (TRDD-478d9687).
c-jira
Manage Jira issues using jira (jira-cli). List and filter issues, create new tickets, transition issue status, manage sprints, and add comments — all from the terminal without opening a browser.
scheduler
Manage scheduled jobs — create, update, list, run remote agents on cron. Use when setting up recurring tasks, checking job status, or managing automation.