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 agentmods add skills/tracer-cloud/opensre/workflownpx skills add Tracer-Cloud/opensre --skill workflowgit clone --depth 1 https://github.com/Tracer-Cloud/opensreWhat 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 | $0.00028 | $0.00341 |
| Opus 5 | $0.00014 | $0.00170 |
| Sonnet 5 | $0.00006 | $0.00068 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
github-workflow 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 2d 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
GitHub Workflow
Use this workflow when the user asks about GitHub engineering status, PR readiness, community follow-ups, or turning an explicit Slack request into a GitHub issue.
- Read before reporting. Use the read-only GitHub tools first, and treat missing or failed reads as incomplete status rather than proof that there are no blockers.
- Report or summarize from known data. Use
generate_work_status_reportfor Slack-ready status andsummarize_community_followupsfor unanswered contributor questions or agenda items. - Propose mutations before execution. Use
propose_github_issue_mutation_from_slackonly for explicit Slack-sourced create, update, or close requests. - Execute only through approval.
execute_github_issue_mutationis the only mutating GitHub workflow tool. It is never an investigation action and must remain chat-only, approval-gated, and proposal-driven. - For ad-hoc
gh(flexible issue/PR/api ops outside this Slack proposal flow), usegithub_cli— nevershell_runwith rawgh.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 33 lines · 28 tokens per session scan A b195ce5164fa
github-workflow is a skill published in the GitHub repository Tracer-Cloud/opensre (10,985 stars, last pushed today), licensed Apache-2.0. It adds 28 tokens to every session and 341 once invoked, about $0.0001 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
host_bash
设备上跑只读 shell 命令做诊断探索（沙箱化 / read-only policy）.
host_restart_service
重启允许列表内的 systemd service（mutating，触发 reviewer 二审）.
file_inspector
Inspect files on the host filesystem.
edge_disk_audit
Audit disk usage on edge devices.
future_skill
A skill that uses fields ongrid does not yet recognize.
hello-world
Skill whose name uses a dash, expected to be normalized.