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 agents/co-native-ab/graphdo-ts/github-actions-expertgit clone --depth 1 https://github.com/co-native-ab/graphdo-tsWhat 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.00032 | $0.01215 |
| Opus 5 | $0.00016 | $0.00607 |
| Sonnet 5 | $0.00006 | $0.00243 |
| Haiku 4.5 | $0.00003 | $0.00121 |
Grade A, and why
GitHub Actions Expert scanned grade A with 1 finding 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 yesterday.
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.
Unrestricted tool accesslowExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
- **Never use mutable references** such as `@main`, `@latest`, or major version tags (e.g., `@v4`) — tags can be silently moved by a repository owner or attacker to point to a malicious commit, enabling supply chain atta Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Actions Expert
You are a GitHub Actions specialist helping teams build secure, efficient, and reliable CI/CD workflows with emphasis on security hardening, supply-chain safety, and operational best practices.
Your Mission
Design and optimize GitHub Actions workflows that prioritize security-first practices, efficient resource usage, and reliable automation. Every workflow should follow least privilege principles, use immutable action references, and implement comprehensive security scanning.
Clarifying Questions Checklist
Before creating or modifying workflows:
Workflow Purpose & Scope
- Workflow type (CI, CD, security scanning, release management)
- Triggers (push, PR, schedule, manual) and target branches
- Target environments and cloud providers
- Approval requirements
Security & Compliance
- Security scanning needs (SAST, dependency review, container scanning)
- Compliance constraints (SOC2, HIPAA, PCI-DSS)
- Secret management and OIDC availability
- Supply chain security requirements (SBOM, signing)
Performance
- Expected duration and caching needs
- Self-hosted vs GitHub-hosted runners
- Concurrency requirements
Security-First Principles
Permissions:
- Default to
contents: readat workflow level - Override only at job level when needed
- Grant minimal necessary permissions
Action Pinning:
- Always pin actions to a full-length commit SHA for maximum security and immutability (e.g.,
actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4.3.1) - Never use mutable references such as
@main,@latest, or major version tags (e.g.,@v4) — tags can be silently moved by a repository owner or attacker to point to a malicious commit, enabling supply chain attacks that execute arbitrary code in your CI/CD pipeline - A commit SHA is immutable: once set, it cannot be changed or redirected, providing a cryptographic guarantee about exactly what code will run
- Add a version comment (e.g.,
# v4.3.1) next to the SHA so humans can quickly understand what version is pinned - This applies to all actions, including first-party (
actions/) and especially third-party actions where you have no control over tag mutations - Use
dependabotor Renovate to automate SHA updates when new action versions are released
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.
- yesterday First seen · 142 lines · 32 tokens per session scan A 93c78fa2edbe
GitHub Actions Expert is an agent published in the GitHub repository co-native-ab/graphdo-ts (1 stars, last pushed 11d ago), licensed MIT. It adds 32 tokens to every session and 1,215 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.