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 openshift-online/gcp-hcp --skill ai-sdlc-pilot-updategit clone --depth 1 https://github.com/openshift-online/gcp-hcpWrote 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/openshift-online/gcp-hcp/ai-sdlc-pilot-update)<a href="https://agentmods.dev/skills/openshift-online/gcp-hcp/ai-sdlc-pilot-update"><img src="https://agentmods.dev/badge/skills/openshift-online/gcp-hcp/ai-sdlc-pilot-update/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/openshift-online/gcp-hcp/ai-sdlc-pilot-update"><img src="https://agentmods.dev/badge/skills/openshift-online/gcp-hcp/ai-sdlc-pilot-update.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.00037 | $0.01858 |
| Opus 5 | $0.00018 | $0.00929 |
| Sonnet 5 | $0.00007 | $0.00372 |
| Haiku 4.5 | $0.00004 | $0.00186 |
Grade A, and why
ai-sdlc-pilot-update 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 11d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agentic SDLC Pilot Update Skill
Gather data from Jira and GitHub, draft a biweekly update comment, get user input on subjective sections, and post the final comment to GCP-579.
Tracking issue: GCP-579 ("Establish AI-Native Developer Experience — Agentic SDLC Pilot") Deadline: June 30, 2026
Phase 1: Gather Jira Activity (BFS traversal)
Determine the lookback window. Default is 14 days. If $days was provided, use that value instead. If $days is missing, non-numeric, or less than 1, fall back to 14.
Compute:
end_date= today's datestart_date= today minus lookback days
BFS traversal starting at GCP-579:
Use a queue-based BFS. Start with ["GCP-579"].
Before traversal, fetch and store GCP-579's own fields (summary, description, status, issuetype, assignee, created, updated).
For each key in the queue:
- Search Jira for direct children using JQL:
parent = KEY ORDER BY updated DESC- Fetch up to 50 results per query; paginate if more exist (pagination applies per parent-key search, not once globally)
- Fetch each child's key, summary, description, status, assignee, issuetype, created, updated fields
- Add each child's key to the queue
- Continue until the queue is empty
After collecting all keys in the hierarchy (including GCP-579 itself, with fields stored for each):
For each discovered key (in groups of 20), fetch the issue's changelog and extract status transitions. Filter transitions to those whose timestamp falls within the lookback window.
Classify findings:
- Completed issues: status transitioned to "Done", "Closed", or "Resolved" within the window
- Created issues:
createdfield is within the window - Status transitions: any status change within the window (excluding completions)
- Blocked issues: status is "Blocked" or summary/description contains "blocked" (case-insensitive)
Phase 2: Gather GitHub Activity
Repos to search:
openshift-online/gcp-hcpopenshift-online/gcp-hcp-infraopenshift-eng/ai-helpersopenshift-online/gcp-hcp-priv(may have restricted access; skip gracefully if unavailable)
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.
- 11d ago First seen · 175 lines · 37 tokens per session scan A 933b98972bbf
ai-sdlc-pilot-update is a skill published in the GitHub repository openshift-online/gcp-hcp (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 37 tokens to every session and 1,858 once invoked, about $0.0002 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-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.