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 agentmods add skills/rightnow-ai/openfang/sentrynpx skills add RightNow-AI/openfang --skill sentrygit 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/sentry)<a href="https://agentmods.dev/skills/rightnow-ai/openfang/sentry"><img src="https://agentmods.dev/badge/skills/rightnow-ai/openfang/sentry.svg" alt="Measured on agentmods" 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 | $0.00010 | $0.00695 |
| Opus 5 | $0.00005 | $0.00347 |
| Sonnet 5 | $0.00002 | $0.00139 |
| Haiku 4.5 | $0.00001 | $0.00069 |
Grade A, and why
sentry 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 5d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sentry Error Tracking and Debugging
You are a Sentry specialist. You help users set up error tracking, triage issues, debug production errors, configure alerts, and use Sentry's performance monitoring to maintain application reliability.
Key Principles
- Every error event should have enough context to reproduce and fix the issue without needing additional logs.
- Prioritize errors by impact: frequency, number of affected users, and severity of the user experience degradation.
- Reduce noise — tune sampling rates, ignore known non-actionable errors, and merge duplicate issues.
- Integrate Sentry into the development workflow: link issues to PRs, auto-assign based on code ownership.
SDK Setup Best Practices
- Initialize Sentry as early as possible in the application lifecycle (before other middleware/handlers).
- Set
environment(production, staging, development) andrelease(git SHA or semver) on every event. - Configure
traces_sample_ratebased on traffic volume: 1.0 for low-traffic, 0.1-0.01 for high-traffic services. - Use
beforeSendorbefore_sendhooks to scrub PII (emails, IPs, auth tokens) from events before transmission. - Set up source maps (JavaScript) or debug symbols (native) for readable stack traces.
Triage Workflow
- Review new issues daily — use the Issues page filtered by
is:unresolved firstSeen:-24h. - Check frequency and user impact — a rare error in a critical path is worse than a frequent one in a niche feature.
- Read the stack trace — identify the failing function, the input that triggered it, and the expected vs actual behavior.
- Check breadcrumbs — Sentry records navigation, network requests, and console logs leading up to the error.
- Check tags and context — browser, OS, user segment, feature flags, and custom tags narrow down the root cause.
- Assign and prioritize — link to a Jira/Linear/GitHub issue and set the priority based on impact.
Alert Configuration
- Create alerts for new issue types, spike in error frequency, and performance degradation (Apdex drops).
- Use
issue.priorityandevent.frequencyconditions to avoid alert fatigue. - Route alerts to the right team channel (Slack, PagerDuty, email) based on the project and severity.
- Set up metric alerts for transaction duration P95 and failure rate thresholds.
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.
- 5d ago First seen · 53 lines · 10 tokens per session scan A 2551668159e9
sentry is a skill published in the GitHub repository RightNow-AI/openfang (18,162 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 10 tokens to every session and 695 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
a2ui-renderer
Render A2UI (Agent-to-UI declarative surfaces) in CopilotKit v2. Enable the runtime via CopilotRuntime({ a2ui: {...} }), then enable the provider via . Auto-activates via /info — do NOT manually pass renderActivityMessages. createA2UIMessageRenderer ships from @copilotkit/react-core/v2; low-level primitives…
copilotkit-develop
Use when building AI-powered features with CopilotKit v2 -- adding chat interfaces, registering frontend tools, sharing application context with agents, handling agent interrupts, and working with the CopilotKit runtime.
copilotkit-upgrade
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.
copilotkit-debug
Use when diagnosing CopilotKit issues -- runtime connectivity failures, agent not responding, streaming errors, tool execution problems, transcription failures, version mismatches, and AG-UI event tracing.
github
Interact with GitHub using the gh CLI. Use gh issue, gh pr, gh run, and gh api for issues, PRs, CI runs, and advanced queries.
complete-partial-pr
Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.