worker-census-report

worker-census-report is a skill for Claude Code, Codex from check-technologies/mcp-server-check. It costs 88 tokens per session (1,815 once invoked), scanned A, original, MIT.

A report that lists a company's employees and contractors, with details such as addresses, the last four digits of Social Security numbers, start dates, workplaces, and status.

In plain words
What is it for?
Use it to prepare benefits-enrollment lists, compliance-audit records, or annual workforce reviews, with filters for worker type and status.
Why use it?
It gathers worker information into one structured document for reviews and administrative checks.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/check-technologies/mcp-server-check/worker-census-report
Any agent
npx skills add check-technologies/mcp-server-check --skill worker-census-report
Clone the repo
git clone --depth 1 https://github.com/check-technologies/mcp-server-check

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for worker-census-report

README.md
[![agentmods](https://agentmods.dev/badge/skills/check-technologies/mcp-server-check/worker-census-report.svg)](https://agentmods.dev/skills/check-technologies/mcp-server-check/worker-census-report)
Your own site
<a href="https://agentmods.dev/skills/check-technologies/mcp-server-check/worker-census-report"><img src="https://agentmods.dev/badge/skills/check-technologies/mcp-server-check/worker-census-report.svg" alt="Measured on agentmods" height="20"></a>
Per session 88 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,815 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00088 $0.01815
Opus 5 $0.00044 $0.00907
Sonnet 5 $0.00018 $0.00363
Haiku 4.5 $0.00009 $0.00181

Measured 5d ago against content hash 7f782958a6a8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

worker-census-report 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.

example-skills/worker-census-report/SKILL.md · 207 lines

How it starts

The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Worker Census Report

This skill generates a complete census of all employees and contractors for a company. It pulls full worker details and presents a structured report suitable for benefits enrollment, compliance audits, and annual reviews.

Prerequisites

Collect from the user:

  1. A Check company ID (looks like com_XXXXXXXXXXXXXXXXXX). Ask for it if not provided.
  2. Optional filters — ask the user:
    • Worker types: employees only, contractors only, or both (default: both)
    • Status filter: active only, terminated only, or all (default: all)

Step 1: Gather Company Context

Pull the company details:

run_tool: get_company { "company_id": "<company_id>" }

Note the company name for the report header.

Step 2: Build Workplace Lookup

Fetch all workplaces to map workplace IDs to addresses:

run_tool: list_workplaces { "company": "<company_id>", "limit": 500 }

Build a lookup table: { workplace_id: { name, line1, city, state, postal_code } }.

If any workplace entry lacks address details, fetch it individually:

run_tool: get_workplace { "workplace_id": "<workplace_id>" }

Step 3: Fetch Employees

Skip this step if the user requested contractors only.

3a. List all employees

run_tool: list_employees { "company": "<company_id>", "limit": 100 }

If the response includes a next cursor, paginate:

run_tool: list_employees { "company": "<company_id>", "limit": 100, "cursor": "<cursor>" }

Continue until all employees are fetched. Report progress for large companies: "Fetched 100/247 employees..."

3b. Get full details for each employee

The list endpoint returns summary data. For full details (residence, SSN last 4, etc.), fetch each employee individually:

run_tool: get_employee { "employee_id": "<employee_id>" }

Process these in batches and give progress updates (e.g., "Fetching employee details: 25/50...").

3c. Apply status filter

If the user requested active only, filter out employees with a termination_date. If terminated only, keep only those with a termination_date.

Read the full file on GitHub · 207 lines

Changes

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.

  1. 5d ago First seen · 207 lines · 88 tokens per session scan A 7f782958a6a8

Subscribe to this mod's changes

worker-census-report is a skill published in the GitHub repository check-technologies/mcp-server-check (18 stars, last pushed 7d ago), licensed MIT. It adds 88 tokens to every session and 1,815 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens