headcount is an organization of independently installable Claude Code plugins, each grouping skills for a department such as finance, security, or demand generation. Claude Code users install the departments they need and invoke their skills for specialized work; the catalogue entries are skills and related agent tooling from that organization.
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 agentmods add skills/cbrock84/headcount/intellectual-propertynpx skills add cbrock84/headcount --skill intellectual-propertygit clone --depth 1 https://github.com/cbrock84/headcountWrote 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/cbrock84/headcount/intellectual-property)<a href="https://agentmods.dev/skills/cbrock84/headcount/intellectual-property"><img src="https://agentmods.dev/badge/skills/cbrock84/headcount/intellectual-property.svg" alt="Measured on agentmods" 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.00091 | $0.00956 |
| Opus 5 | $0.00046 | $0.00478 |
| Sonnet 5 | $0.00018 | $0.00191 |
| Haiku 4.5 | $0.00009 | $0.00096 |
Grade A, and why
intellectual-property 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 2d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Intellectual property
Most IP damage is done quietly and early — by a name adopted without a search, a contractor agreement missing an assignment clause, or a dependency added without reading its license. All three are cheap to prevent and expensive to unwind.
This structures the questions and the recurring failure patterns. IP rights are jurisdictional, deadline-driven and fact-specific — get qualified counsel before adopting a name, filing anything, or responding to a claim.
The four rights protect different things and are not interchangeable
- Trademark protects a name or mark as an indicator of source, within classes of goods and services and within territories. Rights come from use and are strengthened by registration.
- Copyright protects expression, not ideas. It arises automatically on creation; registration matters mainly for what you can recover in a dispute.
- Patent protects an invention, in exchange for publishing it, and is defeated by your own prior public disclosure in many regimes. If patenting is plausible, file before you present, publish, or demonstrate.
- Trade secret protects information whose value depends on being secret, for as long as you actually keep it secret — which requires demonstrable measures, not just intent.
Clear a name before you build on it
A search is cheap; a rebrand after launch is not, and the cost lands after you have printed material, bought domains, and built recognition. Search registered marks in the classes and territories you will operate in, and check for confusingly similar marks rather than exact matches.
Domain availability tells you nothing about trademark risk. Neither does the absence of a company with that exact name.
Establish ownership of work you paid for, in writing, before it starts
This is the most common and most avoidable failure in the whole area.
- Employee work is often owned by the employer by default, but the default varies by jurisdiction and by whether the work relates to the job.
- Contractor and agency work is usually owned by the contractor unless the agreement assigns it. A paid invoice is not an assignment. Logos, code, photography, and copy commissioned without an assignment clause routinely turn out to be licensed rather than owned — discovered during diligence, at the worst possible time.
- Get assignment plus a waiver of moral rights where they apply, and confirm the contractor had the right to assign anything they incorporated.
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.
- 2d ago First seen · 85 lines · 91 tokens per session scan A e3c24f220c8e
intellectual-property is a skill published in the GitHub repository cbrock84/headcount (1,284 stars, last pushed 3d ago), licensed MIT. It adds 91 tokens to every session and 956 once invoked, about $0.0005 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
save
Save durable decisions, findings, plans, and implementation knowledge from the visible Codex conversation into a new or existing NeatContext context. Use only when the user explicitly invokes this skill or asks to preserve the current conversation as reusable context.
mode
Show or set NeatContext routing to auto, ask, or manual for Codex, with an optional default shared with every other NeatContext host. Use only when the user explicitly invokes this skill or clearly asks to change routing behavior.
status
Report the NeatContext context and routing mode active in Codex, including missing-file or stale-routing warnings. Use when the user asks which context is connected or explicitly invokes this skill.
list
List the local NeatContext Contexts available to Codex. Use when the user asks what contexts exist, what can be connected, or explicitly invokes this skill.
hermes-agent-compatibility
Audit Socket-to-Hermes compatibility across Agent Skills, Codex plugins, MCP, hooks, apps, agents, and Hermes extension systems. Use for skill exports, config translations, and Hermes adapter decisions.
build-oxpecker-web-app
Build or modify an Oxpecker web application in idiomatic F#, using endpoint routing, functional EndpointHandler and EndpointMiddleware composition, ASP.NET Core metadata, and focused endpoint tests.