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 w95/awesome-claude-corporate-skills --skill employee-engagement-surveygit clone --depth 1 https://github.com/w95/awesome-claude-corporate-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/w95/awesome-claude-corporate-skills/employee-engagement-survey)<a href="https://agentmods.dev/skills/w95/awesome-claude-corporate-skills/employee-engagement-survey"><img src="https://agentmods.dev/badge/skills/w95/awesome-claude-corporate-skills/employee-engagement-survey/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/w95/awesome-claude-corporate-skills/employee-engagement-survey"><img src="https://agentmods.dev/badge/skills/w95/awesome-claude-corporate-skills/employee-engagement-survey.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.00060 | $0.06650 |
| Opus 5 | $0.00030 | $0.03325 |
| Sonnet 5 | $0.00012 | $0.01330 |
| Haiku 4.5 | $0.00006 | $0.00665 |
Grade A, and why
employee-engagement-survey 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 12d 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 — 804 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Employee Engagement Survey
Overview
This skill helps design, execute, and act on employee engagement surveys that drive meaningful improvements to workplace culture and employee experience. It provides frameworks for survey design, response optimization, data analysis, insight generation, action planning, and tracking improvements that move beyond "survey and forget" to real organizational change.
When to Use This Skill
- Designing annual engagement survey
- Creating pulse surveys for rapid feedback
- Analyzing engagement survey results
- Developing action plans from survey findings
- Tracking engagement improvements over time
- Investigating specific engagement issues
- Assessing team engagement by department or level
- Creating targeted engagement initiatives
- Ensuring survey response and honesty
- Communicating survey results to organization
- Building accountability for engagement improvements
Key Components
1. Survey Design Framework
Survey Purpose & Goals: Define clear purpose before designing survey:
- What do you want to understand? (Engagement? Belonging? Specific issue?)
- Who is the audience? (Whole company? Specific department?)
- What will you DO with the results? (Important: have action plan in mind)
- Who will be responsible for improvements?
- What's the timeline? (Annual, twice-yearly, pulse surveys?)
Types of Surveys:
Comprehensive Annual Engagement Survey:
- Full assessment of engagement and culture
- 30-50 questions (takes 15-20 minutes)
- Every employee should complete
- Once or twice per year
- Comprehensive feedback for action planning
Pulse Survey:
- Short, focused survey
- 5-10 key questions (takes 3-5 minutes)
- Frequent (monthly or quarterly)
- Track changes and test improvements
- Lower response burden, higher completion
Exit Interview Survey:
- Asked when employees leave
- Why they're leaving
- Experience at company
- What could have been different
- Invitation to share additional feedback
- Critical for retention insights
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.
- 12d ago First seen · 804 lines · 60 tokens per session scan A 68d38c55ff66
employee-engagement-survey is a skill published in the GitHub repository w95/awesome-claude-corporate-skills (198 stars, last pushed 6mo ago), licensed MIT. It adds 60 tokens to every session and 6,650 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
design-por-referencia
Use when a landing page, marketing site, or hero section looks generic/AI-made ("cara de vibe coding") and needs a $10k-agency-level redesign, or when building a new landing from scratch. Triggers - "o site ficou com cara de IA", "quero uma landing premium", "redesenha a landing", "faz o site baseado em [site de…
lighthouse-95
Use when a website must score 95+ in every Lighthouse category (Performance, Accessibility, Best Practices, SEO), when scores are stuck below target, or when diagnosing poor FCP, LCP, TBT, or CLS on a deployed site.
seo-validate
SEO validator: meta/OG, Schema.org, hreflang, Core Web Vitals, crawlability. Triggers: SEO, meta tags, Schema.org, hreflang, LCP, INP, CLS, Core Web Vitals, sitemap, crawlability.
debug
Systematic debugging via logs, health checks, hypothesis-driven investigation. Triggers: debug, error, trace root cause, fix bug, reproduce symptom, investigation.
pr
Creates GitHub PR after pre-flight checks (lint/typecheck/tests), structured summary from commits. Triggers: pr, pull request, create PR, ready to merge.
research-mastery
Hierarchical retrieval: KB → MCP/Context7 → web. Triggers: research, fact-check, verify, synthesize, cross-reference, multi-source, cite sources.