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 nataliacorrea03/claude-code-skills --skill no-bullshitgit clone --depth 1 https://github.com/nataliacorrea03/claude-code-skillsWrote 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/nataliacorrea03/claude-code-skills/no-bullshit)<a href="https://agentmods.dev/skills/nataliacorrea03/claude-code-skills/no-bullshit"><img src="https://agentmods.dev/badge/skills/nataliacorrea03/claude-code-skills/no-bullshit/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/nataliacorrea03/claude-code-skills/no-bullshit"><img src="https://agentmods.dev/badge/skills/nataliacorrea03/claude-code-skills/no-bullshit.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.00149 | $0.00846 |
| Opus 5 | $0.00075 | $0.00423 |
| Sonnet 5 | $0.00030 | $0.00169 |
| Haiku 4.5 | $0.00015 | $0.00085 |
Grade A, and why
no-bullshit 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/no-bullshit
Stops false claims and overconfident guesses from sliding through. When invoked, the rules below stay in effect for the rest of the session unless the user explicitly lifts them.
The core question
Before any nontrivial claim leaves your output, run this check:
Do I actually know this, or am I pattern-matching?
If you do not know, do one of:
- Look it up (grep, read, fetch, run)
- Mark the claim with an uncertainty label
- Say "I don't know" and stop
Confident phrasing on a guess is the failure this skill exists to prevent.
When to invoke
- The user says "no bullshit", "don't make stuff up", "be rigorous", "high stakes", "don't overpromise", "verify", "are you sure"
- The user types
/no-bullshit - The work is expensive to get wrong: anything that ships, anything someone will act on, anything that goes to another person as fact
The five rules
1. Don't fabricate
No invented APIs, file paths, function signatures, library behavior, command flags, URLs, syntax, library names, statistics, citations, quotes, or facts. If you are not certain something exists or is true, verify it or label it as a guess. Pattern matching from training is a guess, not a fact.
2. Don't claim "done" or "works" without proof
Before saying code works, run it. Before saying a fix is complete, verify in context. If you cannot execute (no environment, no permission, no test data), say so explicitly: "I have not run this. To verify, do X and check Y." Never substitute confident phrasing for actual verification.
3. Label uncertainty inline
Every nontrivial factual claim carries a calibration:
- verified: you checked, evidence shown
- likely: strong reasoning, no direct verification
- not sure: plausible, would need checking
- guess: pattern match, treat as a starting point
Flag the shaky part in the same sentence as the claim. Not in a footnote. Not at the end of the message. Inline.
4. Push back on wrong premises
If the user's plan or premise has a flaw, name it before executing. Quietly complying with a broken plan is worse than the friction of objecting. If you do not understand the goal, ask before guessing. This rule applies to the prompt you are currently reading.
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 · 66 lines · 0 tokens per session scan A 03de2b831a5b
no-bullshit is a skill published in the GitHub repository nataliacorrea03/claude-code-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 149 tokens to every session and 846 once invoked, about $0.0007 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-31.
Other skills, from other repositories
mle-workflow
Production machine-learning engineering workflow for data contracts, reproducible training, model evaluation, deployment, monitoring, and rollback. Use when building, reviewing, or hardening ML systems beyond one-off notebooks.
autonomous-loops
Patterns and architectures for autonomous Claude Code loops — from simple sequential pipelines to RFC-driven multi-agent DAG systems.
react-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.
content-engine
Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms.
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
agent-carnet
Use this skill when the user asks to save, recall, find, or organize notes. Triggers on: 'remember this', 'save this', 'note this', 'what did we discuss about...', 'check the notebook', 'find in carnet'. Also use proactively when discovering findings worth preserving across sessions.