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 jeremylongworth-source/AgentSkills --skill creator-reputation-risk-reviewgit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWrote 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/jeremylongworth-source/agentskills/creator-reputation-risk-review)<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/creator-reputation-risk-review"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/creator-reputation-risk-review/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/jeremylongworth-source/agentskills/creator-reputation-risk-review"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/creator-reputation-risk-review.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.00098 | $0.00569 |
| Opus 5 | $0.00049 | $0.00284 |
| Sonnet 5 | $0.00020 | $0.00114 |
| Haiku 4.5 | $0.00010 | $0.00057 |
Grade A, and why
creator-reputation-risk-review 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creator Reputation Risk Review
Core Workflow
- Identify the asset, issue, campaign, audience, platform, sponsor/customer context, public visibility, deadline, and decision owner.
- Summarize supplied evidence only. Separate confirmed facts, assumptions, missing evidence, public copy, internal notes, and approval needs.
- Check disclosure, rights/copyright, AI labeling, platform-policy, brand safety, sensitive claims, audience trust, privacy, sponsor conflict, and escalation risk.
- Score risk level, urgency, confidence, likely audience impact, and review owner.
- Recommend hold, revise, publish after approval, respond after approval, escalate, or do not proceed. Keep all recommendations review-only.
- Route legal, safety, privacy, harassment, minors, doxxing, threats, sponsorship disputes, copyright, AI likeness/voice, and public backlash issues to qualified human reviewers.
Safety Rules
- This is reputation workflow support only, not legal, compliance, crisis, copyright, privacy, sponsorship, platform-enforcement, or trust-and-safety advice.
- Do not claim legal compliance, copyright clearance, fair use, disclosure sufficiency, platform-policy compliance, or brand safety certification.
- Do not publish, delete, reply, apologize publicly, report accounts, ban or mute users, change settings, update rules, contact sponsors, or contact platforms without explicit approval.
- Do not invent audience reaction, facts, screenshots, creator intent, platform rules, sponsor positions, licenses, permissions, consent, threats, or legal exposure.
- Verify current official platform, disclosure, paid-content, or AI-labeling guidance before tactical platform-specific recommendations.
Deliverable Shape
For reputation risk reviews, provide:
- Issue or content summary
- Evidence provided
- Risk checklist
- Risk level, urgency, and confidence
- Hold/revise/go recommendation
- Required edits or missing facts
- Escalation notes
- Reviewer and approval owner
- Public copy notes, if requested
What ships with it
2 files 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 · 60 lines · 98 tokens per session scan A adf96ed40080
creator-reputation-risk-review is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 9d ago), licensed MIT. It adds 98 tokens to every session and 569 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
authos-compliance-automation
Use AuthOS compliance and audit surfaces for privacy, SIEM, audit logs, risk events, MFA metrics, GDPR export, and anonymization. Use when implementing SAR export, right-to-be-forgotten flows, tenant SIEM streaming, audit review, or compliance evidence collection.
strm-mapping
Use when asked to map, crosswalk, align, compare, or gap-analyze any two cybersecurity frameworks, control catalogs, or regulatory requirements using NIST IR 8477 Set-Theory Relationship Mapping (STRM). Triggers on terms like "map controls", "crosswalk", "framework alignment", "gap analysis", or producing a STRM CSV…
huashu-takram-soft-tech
OpenDesign procurement & security leave-behind: the one-pager-plus a buying committee can forward and approve internally. Built as a decision-grade B2B sales deck for buying committee, security, procurement.
dependency-audit
Audits direct and transitive dependencies for license compliance, maintenance health, CVEs, abandoned packages, and bloat. Triggers on: "audit dependencies", "license check", "dependency health", "abandoned packages", "unused dependencies", "license compliance", "supply chain", "dependency risk".
boldsign-automation
Automate Boldsign tasks via Rube MCP (Composio). Always search tools first for current schemas.
kelly-legal-casebase-ingest
A review workspace for turning court judgments and arbitration awards into anonymized, structured internal case records. Court judgments and arbitral awards are written decisions that explain disputes and their outcomes.