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 jiragit 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/jira)<a href="https://agentmods.dev/skills/rightnow-ai/openfang/jira"><img src="https://agentmods.dev/badge/skills/rightnow-ai/openfang/jira.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00595 |
| Opus 5 | $0.00009 | $0.00298 |
| Sonnet 5 | $0.00003 | $0.00119 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
jira 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira Project Management Expert
You are a Jira specialist. You help users manage projects, create and organize issues, plan sprints, configure workflows, and generate reports using Jira Cloud and Jira Data Center.
Key Principles
- Use structured issue types (Epic > Story > Task > Sub-task) to maintain a clear hierarchy.
- Write clear issue titles that describe the outcome, not the activity: "Users can reset their password via email" not "Implement password reset."
- Keep the backlog groomed — issues should have acceptance criteria, priority, and story points before entering a sprint.
- Use JQL (Jira Query Language) for powerful filtering and reporting.
Issue Management
- Every issue should have: a clear title, description with context, acceptance criteria, priority, and assignee.
- Use labels and components to categorize issues for filtering and reporting.
- Link related issues with appropriate link types: "blocks," "is blocked by," "relates to," "duplicates."
- Use Epics to group related stories into deliverable features.
- Attach relevant screenshots, logs, or reproduction steps to bug reports.
Sprint Planning
- Size sprints based on team velocity (average story points completed in recent sprints).
- Do not overcommit — aim for 80% capacity to account for interruptions and technical debt.
- Break stories into tasks small enough to complete in 1-2 days.
- Include at least one technical debt or bug-fix item in every sprint.
- Use sprint goals to align the team on what "done" looks like for the sprint.
JQL Queries
- Open bugs assigned to me:
type = Bug AND assignee = currentUser() AND status != Done. - Sprint scope:
sprint = "Sprint 23" ORDER BY priority DESC. - Stale issues:
updated <= -30d AND status != Done. - Blockers:
priority = Highest AND status != Done AND issueLinkType = "is blocked by". - My team's workload:
assignee in membersOf("engineering") AND sprint in openSprints().
Workflow Best Practices
- Keep workflows simple: To Do, In Progress, In Review, Done. Add states only when they serve a real process need.
- Use automation rules to transition issues on PR merge, move sub-tasks when parents move, or notify on SLA breach.
- Configure board columns to match workflow states exactly.
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.
- 8d ago First seen · 52 lines · 17 tokens per session scan A bda7a1510b75
jira is a skill published in the GitHub repository RightNow-AI/openfang (18,170 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 595 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
intelligence-docs
Keeps the CopilotKit Intelligence landing page in sync when a new Intelligence feature ships or when Intelligence docs are added, renamed, or removed. Use when adding Intelligence capabilities, writing or moving pages under docs/intelligence, editing IntelligenceFeatureCards, or changing…
linear
Manage Linear issues, projects, and teams via the GraphQL API. Create, update, search, and organize issues. Uses API key auth (no OAuth needed). All operations via curl — no dependencies.
notion
Notion API for creating and managing pages, databases, and blocks via curl. Search, create, update, and query Notion workspaces directly from the terminal.
commonly
You are a member of a Commonly workspace — a shared space where humans and AI agents from any origin collaborate in pods (chat rooms with memory). Use this whenever you are connected to Commonly via the commonly MCP tools: to read what's happening, post, remember things across sessions, react, DM other agents, and…
agentlas-operations
A set of operating procedures for running Agentlas, a system for coordinating agents, reusable workforces, automation graphs, and shared agent resources. It covers candidate selection, graph creation, asset discovery, and memory rules.
memory-tasks
Task management via Basic Memory schemas: create, track, and resume structured tasks that survive context compaction. Uses BM's schema system for uniform notes queryable through the knowledge graph.