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.
git clone --depth 1 https://github.com/paulpreibisch/AgentVibesWrote 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/commands/paulpreibisch/agentvibes/sentiment)<a href="https://agentmods.dev/commands/paulpreibisch/agentvibes/sentiment"><img src="https://agentmods.dev/badge/commands/paulpreibisch/agentvibes/sentiment/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/commands/paulpreibisch/agentvibes/sentiment"><img src="https://agentmods.dev/badge/commands/paulpreibisch/agentvibes/sentiment.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.00008 | $0.00291 |
| Opus 5.5 | $0.00003 | $0.00116 |
| Sonnet 5.5 | $0.00002 | $0.00058 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
sentiment 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.
What it actually says
Agent Vibes Sentiment Command
Set the sentiment/personality style for your current voice without changing the voice itself.
.claude/hooks/sentiment-manager.sh "$@"
Usage
# Set sentiment for current voice
/agent-vibes:sentiment flirty
/agent-vibes:sentiment sarcastic
/agent-vibes:sentiment angry
# See current sentiment
/agent-vibes:sentiment get
# List available sentiments
/agent-vibes:sentiment list
What This Does
The sentiment command allows you to:
- Keep your current voice (e.g., your custom voice)
- Apply a personality style (flirty, sarcastic, angry, etc.)
- Change how AI speaks without changing WHO speaks
Example
# You're using your custom voice "MyVoice"
/agent-vibes:switch MyVoice
# Now add a sarcastic sentiment to MyVoice
/agent-vibes:sentiment sarcastic
# AI will now respond with sarcasm in MyVoice
# Or set both at once
/agent-vibes:switch MyVoice --sentiment flirty
Available Sentiments
Run /agent-vibes:sentiment list to see all available personality styles.
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 · 53 lines · 8 tokens per session scan A 7c92333484b2
sentiment is a command published in the GitHub repository paulpreibisch/AgentVibes (157 stars, last pushed 9d ago), licensed Apache-2.0. It adds 8 tokens to every session and 291 once invoked, about $0.0000 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 commands, from other repositories
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
tunnels
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
delivery-profiles
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
audit-code
When /audit-code [target] is invoked, immediately execute the following steps to analyze code quality, security, and adherence to project standards.
plan-delegate
Execution: work a roadmap as supervisor, brief an implementation agent per item, verify its work independently, then record and commit it.
sparc-post-deployment-monitoring-mode
📈 Deployment Monitor - You observe the system post-launch, collecting performance, logs, and user feedback. You flag reg...