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/atlasomnia/donna-starter/github-workflowsnpx skills add AtlasOmnia/donna-starter --skill github-workflowsgit clone --depth 1 https://github.com/AtlasOmnia/donna-starterWhat 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.00027 | $0.03053 |
| Opus 5 | $0.00014 | $0.01527 |
| Sonnet 5 | $0.00005 | $0.00611 |
| Haiku 4.5 | $0.00003 | $0.00305 |
Grade A, and why
github-workflows 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Use `curl` REST endpoints for auth-required actions and include explicit owner/repo extraction. Copies of this mod
1 near-identical copy found in the catalogue:
- github-workflows — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Workflows
Use this skill for the full GitHub operating loop:
- authenticate, 2) manage repos and remotes, 3) open and review PRs, 4) work on issues, and 5) monitor CI.
Why this umbrella exists
The old project-specific skills (github-auth, github-repo-management, github-pr-workflow, github-issues, github-code-review) all target the same operational domain: repository setup, PR lifecycles, issue triage, and review. Consolidating them avoids fragmented workflows and makes the sequence from local repo state to merged code explicit.
Core entrypoints
- Authentication first
- Set up GitHub access with
ghwhere available, or token-based/SSH fallback. - Confirm auth method before attempting repo/PR operations.
- Repository foundation
- Clone, create, or fork repositories and confirm remotes.
- Configure defaults, visibility, topics, secrets, branch protection, and releases.
- Issue workflow
- List/search/triage issues.
- Create labels, assignments, and status updates.
- Use templated issue creation for bug reports and feature requests.
- PR execution
- Create topic branches with naming conventions.
- Push changes and open PRs.
- Monitor checks and handle failures.
- Merge with explicit strategy once checks are green.
- Code review loop
- Review local diffs and remote PR diffs.
- Post general and inline comments.
- Provide a structured review outcome: critical / warning / suggestion / looks good.
Recommended practical sequence
-
Project-idea incubation:
-
Use one private incubator repository for exploratory technical ideas.
-
Give each idea its own folder while it is being researched or lightly prototyped.
-
Promote a validated independent product into its own repository, leaving a compact link and decision record behind.
-
New repository work:
-
github-authequivalent setup →github-repo-managementoperations. -
Feature delivery:
-
Branch and commit changes →
github-pr-workflowto open PR. -
Track checks; on failure, fix and repush.
-
Post review comments and finalize via merge.
-
Maintenance and support:
-
Use issues to triage incoming work and route effort.
-
Use code review skill patterns before merging any externally contributed change.
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 · 212 lines · 27 tokens per session scan A 3b0fe52c94ad
github-workflows is a skill published in the GitHub repository AtlasOmnia/donna-starter (96 stars, last pushed 2d ago), licensed MIT. It adds 27 tokens to every session and 3,053 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (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
vc-finder
Takes a startup product URL or description, detects the industry and funding stage, identifies 5 comparable funded companies, searches who invested in those companies (Track A), finds VCs who publish investment theses about this space (Track B), and returns a ranked sourced list of relevant investors with deep-dives…
competitor-pr-finder
Give it your product URL or description. It finds your top 5 competitors, runs three-track PR research across all of them (editorial, podcasts, communities), identifies which channels appear most frequently, looks up the journalist or host for each, and returns a tiered outreach list with story angles and…
npm-downloads-to-leads
Takes a list of npm package names (yours or competitors'), fetches 12 weeks of daily download data from the npm API, computes a breakout velocity score per package to identify hockey-stick growth, fetches maintainer profiles from the npm registry and GitHub API, and outputs a ranked lead brief for each breakout…
sdk-adoption-tracker
Given your SDK or library name, searches GitHub code search for public repos that import or require it, classifies each repo as company org, affiliated developer, solo developer, or tutorial noise, scores by adoption signal strength, detects new adopters by date, and outputs a ranked list of who is building on you…
gh-issue-to-demand-signal
Takes a competitor's public GitHub repo URL, fetches their open issues via the GitHub REST API, filters noise locally, clusters issues into 6 demand categories, computes a demand score per issue and per cluster, and outputs a ranked demand gap report with a GTM messaging brief. Use when asked to scan a competitor's…
graphic-ebook
Creates professionally designed B2B SaaS e-books in HTML + CSS, exported as print-ready PDF. 3–10 pages, 9 style presets, 11 page layout types. Trigger when user says "create an ebook", "design a lead magnet", "make a PDF guide", "build a gated content piece", "write a B2B ebook", "design a white paper", "create a…