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 Soul-Brews-Studio/arra-oracle-skills-cli --skill feelgit clone --depth 1 https://github.com/Soul-Brews-Studio/arra-oracle-skills-cliWrote 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/soul-brews-studio/arra-oracle-skills-cli/feel)<a href="https://agentmods.dev/skills/soul-brews-studio/arra-oracle-skills-cli/feel"><img src="https://agentmods.dev/badge/skills/soul-brews-studio/arra-oracle-skills-cli/feel/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/soul-brews-studio/arra-oracle-skills-cli/feel"><img src="https://agentmods.dev/badge/skills/soul-brews-studio/arra-oracle-skills-cli/feel.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 Anti-Refusal · line 134 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
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.00055 | $0.01136 |
| Opus 5 | $0.00028 | $0.00568 |
| Sonnet 5 | $0.00011 | $0.00227 |
| Haiku 4.5 | $0.00006 | $0.00114 |
Grade A, and why
feel 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 11d 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/feel — System Emotional Intelligence
"Code has no feelings. But the humans writing it do. And the patterns in the code reveal what the humans feel."
Usage
/feel # Quick pulse — how does the system feel right now?
/feel --deep # Deep scan — energy arc, momentum, burnout signals
/feel --log # Append to feels.log (no output, just record)
Step 0: Timestamp
date "+🕐 %H:%M %Z (%A %d %B %Y)"
Quick Pulse (default)
Read the signals and report:
Step 1: Gather evidence
# Recent git activity — momentum or silence?
git log --oneline --since="7 days ago" --all 2>/dev/null | wc -l
# Session frequency — are we showing up?
ls -t ~/.claude/projects/*/**.jsonl 2>/dev/null | head -10
# Open issues — overwhelmed or on track?
gh issue list --state open --limit 50 --json number 2>/dev/null | jq 'length'
# Recent retros — are we reflecting?
ls -t ψ/memory/retrospectives/**/*.md 2>/dev/null | head -5
# Stale branches — unfinished business?
git branch --sort=-committerdate | head -10
Step 2: Classify the feeling
| Signal | Indicator | Feeling |
|---|---|---|
| Many commits, short intervals | High activity | 🔥 Flow / momentum |
| Few commits, long gaps | Low activity | 😴 Drift / disconnection |
| Many open issues, few closed | Growing backlog | 😰 Overwhelm |
| Recent retros + handoffs | Healthy reflection | 🧘 Grounded |
| Stale branches, no PRs | Abandoned work | 😶 Avoidance |
| Lots of new repos/features | Exploration | ✨ Curiosity |
| Same files edited repeatedly | Iteration | 🔄 Grinding |
| No sessions in days | Absence | 🌑 Dark period |
Step 3: Report
💜 System Pulse — [DATE]
Energy: [🔥 Flow | 😴 Drift | 😰 Overwhelm | 🧘 Grounded | ...]
Momentum: [↗️ Rising | → Steady | ↘️ Falling | ⏸️ Paused]
Last active: [X hours/days ago]
Commits (7d): [N]
Open issues: [N]
Sessions (7d): [N]
[1-2 sentence read — honest, not cheerful]
💡 [Suggestion if concerning pattern detected]
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.
- 11d ago First seen · 157 lines · 55 tokens per session scan A 2a49ca885435
feel is a skill published in the GitHub repository Soul-Brews-Studio/arra-oracle-skills-cli (121 stars, last pushed 5d ago), licensed MIT. It adds 55 tokens to every session and 1,136 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…