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 ARCASSystems/FounderOS --skill github-opsgit clone --depth 1 https://github.com/ARCASSystems/FounderOSWrote 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/arcassystems/founderos/github-ops)<a href="https://agentmods.dev/skills/arcassystems/founderos/github-ops"><img src="https://agentmods.dev/badge/skills/arcassystems/founderos/github-ops/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/arcassystems/founderos/github-ops"><img src="https://agentmods.dev/badge/skills/arcassystems/founderos/github-ops.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.00067 | $0.01323 |
| Opus 5.5 | $0.00027 | $0.00529 |
| Sonnet 5.5 | $0.00013 | $0.00265 |
| Haiku 4.5 | $0.00007 | $0.00132 |
Grade A, and why
github-ops 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 today.
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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Operations
Runs on: local-exec - runs a local script; on a cloud surface I read the results, I do not run it.
Fast GitHub operations on any repo your gh CLI is authenticated against.
Trigger
When the operator asks about GitHub issues, PRs, repos, actions, or releases.
Interface: gh CLI is canonical
Use the gh CLI via Bash for all read and write operations: gh issue list, gh pr view, gh api, gh run list, and so on. The CLI is the canonical interface for this skill.
A GitHub MCP server, if present in the session, may expose only authenticate and complete_authentication (auth-only) and not the full issue, PR, or Actions tool surface. Do not assume MCP covers an operation. Check the available tools at session start before relying on MCP, and fall back to gh whenever MCP does not cover what you need. If a future session has a fuller GitHub MCP wired up, prefer those tools and fall back to gh only for gaps.
Pre-flight
- Confirm
ghis installed and authenticated:gh auth status. If it is not, tell the operator to rungh auth loginand stop. - Confirm the target repo. If the working directory is a git repo,
ghinfers it. For another repo, pass--repo owner/nameexplicitly.
Capabilities
A title or body holds someone's words, and an issue body often holds code in backticks. Inside double quotes on the command line those backticks and any $(...) run as commands. So never put real text in quotes after --title or --body. Pass the title through a quoted block and the body on stdin with --body-file -, every line at the left edge with no spaces in front:
gh issue create --title "$(cat <<'FOUNDER_OS_TITLE_END'
<the title>
FOUNDER_OS_TITLE_END
)" --body-file - <<'FOUNDER_OS_BODY_END'
<the body, as many lines as it needs>
FOUNDER_OS_BODY_END
gh issue comment <number> and gh pr create take the same --body-file - block (and gh pr create the same --title block). If the text has a line that reads exactly FOUNDER_OS_TITLE_END or FOUNDER_OS_BODY_END, do not run it.
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.
- today Changed · +13 lines 89da463319a7
- 1mo ago First seen · 87 lines · 67 tokens per session scan A b899e5454a66
github-ops is a skill published in the GitHub repository ARCASSystems/FounderOS (6 stars, last pushed yesterday), licensed MIT. It adds 67 tokens to every session and 1,323 once invoked, about $0.0003 per session on Opus 5.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-09-03.
Other skills, from other repositories
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
ct-dev-workflow
Development workflow orchestration for task-driven development with atomic commits, conventional commit messages, and systematic release processes. Enforces task traceability, branch discipline, smart test scope selection, and GitHub Actions integration. Use when committing code, creating releases, managing branches…
smith-build
Autonomous build phase — generates tasks, implements, tests, commits, pushes, merges, and produces release notes. Runs without user interaction.
release-notes
Compare the repository with the team's Folio wiki and write release notes: read git log since the last tag, read the Roadmap table, create or update a Release notes page and add what the roadmap table is missing. Use when asked for release notes or to sync the wiki with the code.
auto-build-loop
Autonomous build driver after SDD spec approval: phase-scoped headless build sessions, driver-owned commits, cross-provider review gates, milestone pauses, and fail-closed escalation — under explicit opt-in autonomy profiles.
git-ship
An automated Git release workflow that takes code changes through a branch, commit, pull request, review checks, squash merge, and return to the main branch. A pull request is a request to review and merge changes into a shared branch.