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 saski/arnesto --skill radical-candorgit clone --depth 1 https://github.com/saski/arnestoWrote 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/saski/arnesto/radical-candor)<a href="https://agentmods.dev/skills/saski/arnesto/radical-candor"><img src="https://agentmods.dev/badge/skills/saski/arnesto/radical-candor/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/saski/arnesto/radical-candor"><img src="https://agentmods.dev/badge/skills/saski/arnesto/radical-candor.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.00073 | $0.00518 |
| Opus 5 | $0.00036 | $0.00259 |
| Sonnet 5 | $0.00015 | $0.00104 |
| Haiku 4.5 | $0.00007 | $0.00052 |
Grade A, and why
radical-candor 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.
This is a copy
100% identical to radical-candor — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
Domain Context
This skill implements a proven product management framework. The approach combines best practices from industry leaders and is designed for practical application in day-to-day PM work.
Input Requirements
- Context about your product, feature, or problem
- Relevant data, research, or constraints (recommended but optional)
- Clear articulation of what you're trying to achieve
Radical Candor
What It Is
Radical Candor is a framework for giving feedback that builds trust and drives results. The core insight: great feedback happens when you Care Personally AND Challenge Directly at the same time.
Most people fail at feedback because they choose one or the other. They're either so focused on being nice that they don't say what needs to be said (ruinous empathy), or they're so focused on being direct that they forget to show they care (obnoxious aggression). Radical Candor isn't about finding a middle ground—it's about doing both fully.
The key shift: Move from "How do I deliver this feedback?" to "How do I help this person succeed?"
When to Use It
Use Radical Candor when you need to:
- Give feedback (both praise and criticism) that actually lands
- Have difficult performance conversations with direct reports
- Build a culture of honest communication on your team
- Solicit feedback from others about your own performance
- Coach employees through growth and development
- Address problems before they become crises
- Build trust in professional relationships
When Not to Use It
- When you don't actually care — if you just want to vent or hurt someone
- When the feedback is about unchangeable personal traits — focus on behavior, not personality
- When you haven't solicited feedback first — always start by asking for feedback
- When you're saving it for a performance review — Radical Candor happens in the moment
Resources
Books:
- Radical Candor by Kim Scott
- Radical Respect by Kim Scott
- When They Win, You Win by Russ Laraway
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 · 52 lines · 73 tokens per session scan A 2e17322d0a86
radical-candor is a skill published in the GitHub repository saski/arnesto (5 stars, last pushed 2d ago), licensed Unlicense. It adds 73 tokens to every session and 518 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to radical-candor, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
work-state-and-delivery
Use when designing or reconciling design docs, task boards, external trackers, execution plans, delivery records, handoffs, review evidence, task-to-change traceability, or repository commit-coupling policy.
flowai-live-dashboard-template
Team-management dashboard skill in the FlowAI aesthetic — three tabs (Team Members, Team Details, Activity Log), KPI stat row, member table, role distribution bar chart, online presence and activity sparklines, and a top-contributors panel, all in a single self-contained HTML file with light/dark theming, hoverable…
team-okrs
OKR tracker page — quarter banner, three objectives with their key results as progress bars, owner avatars, status pills, and a "this quarter at a glance" sidebar. Use when the brief mentions "OKRs", "key results", "objectives", or "目标".
huashu-keynote-black
OpenDesign's all-hands: the year in review, the three priorities, and what every team owns next quarter. Built as a decision-grade corporate strategy deck for whole company.
html-ppt-knowledge-arch-blueprint
OpenDesign's incident retro: the daemon-restart data bug, the root cause, the fix, and the systemic follow-ups. Built as a decision-grade product management deck for engineering, SRE, leadership.
ppt-keynote
An operating-model redesign for a scaling logistics firm — the diagnosis, the target model, and the transition roadmap. Built as a decision-grade consulting deck for client sponsor, ops leaders.