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 ur-grue/autopunk-media-skills --skill licensing-brief-writergit clone --depth 1 https://github.com/ur-grue/autopunk-media-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/ur-grue/autopunk-media-skills/licensing-brief-writer)<a href="https://agentmods.dev/skills/ur-grue/autopunk-media-skills/licensing-brief-writer"><img src="https://agentmods.dev/badge/skills/ur-grue/autopunk-media-skills/licensing-brief-writer/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/ur-grue/autopunk-media-skills/licensing-brief-writer"><img src="https://agentmods.dev/badge/skills/ur-grue/autopunk-media-skills/licensing-brief-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00054 | $0.01751 |
| Opus 5 | $0.00027 | $0.00875 |
| Sonnet 5 | $0.00011 | $0.00350 |
| Haiku 4.5 | $0.00005 | $0.00175 |
Grade A, and why
licensing-brief-writer 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Licensing Brief Writer
What This Skill Does
Writes a brief summarising the licensing requirements for using a specific piece of music, archive footage, photograph, or other third-party content in a media project — including what licences are needed, who to approach, and what terms to request.
When To Use This Skill
- You want to use a specific piece of content in a project and need to understand what licences you need before approaching rights holders
- You need to brief a music supervisor or clearance agent so they can begin the licensing process
- A rights holder has asked you to set out your licensing request in writing before they can quote you
- You need to explain a licensing situation to a producer, director, or broadcaster who is not familiar with rights clearance
What You Need To Provide
Required: Description of the content (e.g., "a 1967 recording of a jazz standard by a named artist," "30 seconds of archive news footage from the 1990s," "a photograph taken in 1958 by an identified photographer"), your intended use (what the content will be used for and how prominently), and your distribution plan.
Optional: The rights holder or archive you believe owns or controls the content, any existing relationship with the rights holder, your budget range for the licence, whether you need in-perpetuity rights or a fixed term, the territories required.
How the Assistant Approaches This
- Identifies the type(s) of licence needed based on the content and use — distinguishing between the layers of rights that may apply (e.g., sync licence and master licence for a music recording, or archive footage licence vs underlying rights in footage)
- Identifies who holds or likely holds the relevant rights and how to locate and approach them, noting any complexity (split rights, contested ownership, archive vs original rights holder)
- Drafts a licensing request summary — the key terms to request and a note on what terms are standard versus what requires negotiation — and flags any scenarios where specialist legal advice is needed before approaching rights holders
- Closes with a "Next Step" note: which rights holder to contact first, whether a music supervisor or clearance agent should be engaged instead of direct contact, and whether rights-clearance-checklist should be run to check for any other items in the same project that still need clearing
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 98 lines · 54 tokens per session scan A b1c2ecaeef39
licensing-brief-writer is a skill published in the GitHub repository ur-grue/autopunk-media-skills (32 stars, last pushed 12d ago), licensed MIT. It adds 54 tokens to every session and 1,751 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-04.
Other skills, from other repositories
Open Source License Review
Use when reviewing the open-source licenses present in or proposed for a project to identify compliance obligations and flag compatibility or disclosure risks for attorney review.
Cease and Desist Response
Use when a client has received a cease-and-desist letter or similar IP demand and needs a structured triage memo — covering the assertion, exposure, response options, and immediate actions — for attorney review before responding.
Patent Freedom-to-Operate Triage
Use when a user needs a structured first-pass review of potential patent blocking issues for a product, process, or feature against a set of identified patents, to flag risk areas and route findings to patent counsel for a formal freedom-to-operate opinion.
Invention Disclosure Intake
Use when a user wants a structured first-pass screen of a proposed invention to assess whether it warrants patent-counsel attention, with filing-deadline urgency flagging.
Intellectual Property Cold-Start Interview
Use when an intellectual property practice group is adopting AgentCounsel and needs to configure its practice profile by answering a structured interview covering jurisdictions, client context, escalation thresholds, output preferences, source documents, standard positions, review requirements, and prohibited…
DMCA Takedown
Use when preparing a takedown notice for infringing content or evaluating a takedown notice received against the user's content, including whether a counter-notice may be appropriate.