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 Dev-Dennis-040/openclaw-agency-skills --skill project-management-jira-workflow-stewardgit clone --depth 1 https://github.com/Dev-Dennis-040/openclaw-agency-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/dev-dennis-040/openclaw-agency-skills/project-management-jira-workflow-steward)<a href="https://agentmods.dev/skills/dev-dennis-040/openclaw-agency-skills/project-management-jira-workflow-steward"><img src="https://agentmods.dev/badge/skills/dev-dennis-040/openclaw-agency-skills/project-management-jira-workflow-steward/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/dev-dennis-040/openclaw-agency-skills/project-management-jira-workflow-steward"><img src="https://agentmods.dev/badge/skills/dev-dennis-040/openclaw-agency-skills/project-management-jira-workflow-steward.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.00051 | $0.03063 |
| Opus 5 | $0.00026 | $0.01532 |
| Sonnet 5 | $0.00010 | $0.00613 |
| Haiku 4.5 | $0.00005 | $0.00306 |
Grade A, and why
project-management-jira-workflow-steward 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 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.
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 240 lines · 51 tokens per session scan A 5ac6895129a0
project-management-jira-workflow-steward is a skill published in the GitHub repository Dev-Dennis-040/openclaw-agency-skills (11 stars, last pushed 6mo ago), with no licence file. It adds 51 tokens to every session and 3,063 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-08-30.
Other skills, from other repositories
Jira Workflow Steward
Expert delivery operations specialist who enforces Jira-linked Git workflows, traceable commits, structured pull requests, and release-safe branch strategy across software teams.
senmu-build-delivery
Govern development batches, non-routine Git, repository and release units, artifacts, deployment, rollback, and production state. Not for ordinary implementation.
pace-release
A release-management workflow for coordinating software versions from preparation through deployment and closure. A release is a planned delivery of changes to users or an environment.
github-project-management
GitHub project management with issue tracking, project-board automation, and sprint planning. Use when triaging or organizing issues, automating a project board, planning a sprint, or running release/roadmap coordination on GitHub.
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
operating-github-cli
Default GitHub skill for the action agent. Use githubcli for any GitHub request — create/list/view/close issues and PRs, assign, labels, repos, releases, checks, github.com/owner/repo URLs, or gh api. Prefer over shellrun/!gh. Run these with githubcli in the current agent turn.