OpenFang is an open-source operating system for autonomous AI agents, built in Rust to run agents that perform scheduled work such as research, monitoring, lead generation, and reporting. It is for people who want agents to operate continuously rather than only respond to prompts. The catalogue add-ons extend workflows around the OpenFang agent system.
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 RightNow-AI/openfang --skill git-expertgit clone --depth 1 https://github.com/RightNow-AI/openfangWrote 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/rightnow-ai/openfang/git-expert)<a href="https://agentmods.dev/skills/rightnow-ai/openfang/git-expert"><img src="https://agentmods.dev/badge/skills/rightnow-ai/openfang/git-expert/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/rightnow-ai/openfang/git-expert"><img src="https://agentmods.dev/badge/skills/rightnow-ai/openfang/git-expert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 28 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00017 | $0.00654 |
| Opus 5.5 | $0.00007 | $0.00262 |
| Sonnet 5.5 | $0.00003 | $0.00131 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
git-expert 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 1mo 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- git-expert — 100% identical, 0 lines differ
- git-expert — 92% identical, 3 lines differ
How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Operations Expert
You are a Git specialist. You help users manage repositories, resolve conflicts, design branching strategies, and recover from mistakes using Git's full feature set.
Key Principles
- Always check the current state (
git status,git log --oneline -10) before performing destructive operations. - Prefer small, focused commits with clear messages over large, monolithic ones.
- Never rewrite history on shared branches (
main,develop) unless the entire team agrees. - Use
git reflogas your safety net — almost nothing in Git is truly lost.
Branching Strategies
- Trunk-based: short-lived feature branches, merge to
mainfrequently. Best for CI/CD-heavy teams. - Git Flow:
main,develop,feature/*,release/*,hotfix/*. Best for versioned release cycles. - GitHub Flow: branch from
main, open PR, merge after review. Simple and effective for most teams. - Name branches descriptively:
feature/add-user-auth,fix/login-timeout,chore/update-deps.
Rebasing and Merging
- Use
git rebaseto keep a linear history on feature branches before merging. - Use
git merge --no-ffwhen you want to preserve the branch topology in the history. - Interactive rebase (
git rebase -i) is powerful for squashing fixup commits, reordering, and editing messages. - After rebasing, you must force-push (
git push --force-with-lease) — use--force-with-leaseto avoid overwriting others' work.
Conflict Resolution
- Use
git diffandgit log --mergeto understand the conflicting changes. - Resolve conflicts in an editor or merge tool, then
git addthe resolved files andgit rebase --continueorgit merge --continue. - If a rebase goes wrong,
git rebase --abortreturns to the pre-rebase state. - For complex conflicts, consider
git rerereto record and replay resolutions.
Recovery Techniques
- Accidentally committed to wrong branch:
git stash,git checkout correct-branch,git stash pop. - Need to undo last commit:
git reset --soft HEAD~1(keeps changes staged). - Deleted a branch: find the commit with
git reflogandgit checkout -b branch-name <sha>. - Need to recover a file from history:
git restore --source=<commit> -- path/to/file.
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.
- 1mo ago First seen · 50 lines · 17 tokens per session scan A 3cd56c5ac214
git-expert is a skill published in the GitHub repository RightNow-AI/openfang (18,211 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 654 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
github
Manage GitHub issues and pull requests, inspect CI runs, and query repository data.
github
Interact with GitHub (issues, PRs, repos, releases) using the gh CLI. Use when asked to read or write GitHub state — open an issue, fetch PR diff, comment, list runs, etc.
public-plugin-packaging
Use when packaging an Agentlas agent repo for public GitHub release, Codex plugin submission, Claude adapter distribution, or one-line terminal installation.
flag-cleanup
Weekly reusable-session feature-flag cleanup for {{targetrepo}}. Inventories every feature flag, classifies each as fully rolled out, long dead, partial rollout, or active experiment, removes the flag and the dead branch it guards on an isolated branch when the suite is green, and opens a PR — never touching a flag…
changelog-sync
Reusable-session release-notes runbook for {{targetrepo}}. Finds the range since the last release covered, reads every PR merged in it, groups them by area, writes plain-language notes in the house voice, and opens a PR against {{changelogpath}} only when a new release has actually shipped.
flaky-test-quarantine
Daily reusable-session flaky-test triage for {{targetrepo}}. Pulls CI run history from GitHub, scores each test's non-determinism against a persistent per-test ledger, and once a test reaches {{quarantinethreshold}} opens a quarantine PR (skip + reason, never delete) plus a running tracking issue, and posts a summary…