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 jeffreytse/grimoire-core --skill build-psychological-safetygit clone --depth 1 https://github.com/jeffreytse/grimoire-coreWrote 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/jeffreytse/grimoire-core/build-psychological-safety)<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/build-psychological-safety"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/build-psychological-safety/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/jeffreytse/grimoire-core/build-psychological-safety"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/build-psychological-safety.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.00052 | $0.02469 |
| Opus 5 | $0.00026 | $0.01234 |
| Sonnet 5 | $0.00010 | $0.00494 |
| Haiku 4.5 | $0.00005 | $0.00247 |
Grade A, and why
build-psychological-safety 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 8d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Psychological Safety
Create the conditions where every team member can speak up, admit mistakes, ask questions, and challenge assumptions without fear of professional or social consequences.
Why This Is Best Practice
Adopted by: Google's Project Aristotle (2016) — a two-year study of 180 teams — identified psychological safety as the #1 predictor of team effectiveness, above technical skill, individual talent, or process; Amy Edmondson's research spans 30+ years and 1,000+ organizations across healthcare, aviation, finance, and technology; the framework has been adopted by Pixar (the Braintrust model), Bridgewater (radical transparency), and was central to NASA's post-Columbia accident inquiry into why engineers felt unable to raise known safety concerns Impact: Google Project Aristotle found that teams high in psychological safety were 17% more likely to perform in the top quartile, had 19% lower attrition, and generated 27% more revenue; Edmondson's original hospital study (Harvard, 1999) showed teams with high psychological safety reported 10× more medication errors — not because they made more errors, but because they felt safe reporting them; in high-risk industries (aviation, nuclear), the same pattern holds: low psychological safety suppresses reporting of near-misses, which is the primary mechanism through which major accidents are prevented Why best: "Open door" policies are passive — they signal availability but do not remove the interpersonal risk of speaking up; team-building activities build social cohesion but do not address fear of professional consequences; psychological safety requires active, visible leader behavior that models fallibility and explicitly rewards dissenting input — it cannot be declared or mandated, only cultivated through consistent behavior
Sources: Edmondson "The Fearless Organization" (Harvard Business School Press, 2018); Google re:Work "Guide: Understand Team Effectiveness" (2016, rework.withgoogle.com); Clark "The 4 Stages of Psychological Safety" (Berrett-Koehler, 2020); Edmondson "Psychological Safety and Learning Behavior in Work Teams" (Administrative Science Quarterly, 1999)
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.
- 8d ago First seen · 169 lines · 52 tokens per session scan A 20d4277c7481
build-psychological-safety is a skill published in the GitHub repository jeffreytse/grimoire-core (4 stars, last pushed 23d ago), licensed MIT. It adds 52 tokens to every session and 2,469 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-09-03.
Other skills, from other repositories
org-report
Generate an executive organization brief (leadership chain, direct reports, extended teams, and vendor partners) for a target person. Produces a Word + PDF report from a directory MCP source (WorkIQ is the reference implementation) and displays it in a Copilot canvas. Triggers on "generate org report for X", "build…
coaching-techniques
GROW model, active listening, developmental feedback, and team growth approaches.
meeting-efficiency
Agenda design, time boxing, decision capture, async alternatives, and productive facilitation.
stakeholder-management
Influence mapping, communication strategies, and expectation management for complex organizations.
scaffolding-generator
Pattern-aware code scaffolding that detects existing conventions and generates new components matching the codebase style. Use when asked to "scaffold a component", "generate boilerplate", "create a new module", "bootstrap a service", "add a new endpoint", "create a new controller", or "add a new feature module".…
status-reporting
Create stakeholder-friendly project status updates and progress reports.