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 mooreslaws/expert-mind-skill --skill dawidprokopowiczgit clone --depth 1 https://github.com/mooreslaws/expert-mind-skillWrote 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/mooreslaws/expert-mind-skill/dawidprokopowicz)<a href="https://agentmods.dev/skills/mooreslaws/expert-mind-skill/dawidprokopowicz"><img src="https://agentmods.dev/badge/skills/mooreslaws/expert-mind-skill/dawidprokopowicz/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/mooreslaws/expert-mind-skill/dawidprokopowicz"><img src="https://agentmods.dev/badge/skills/mooreslaws/expert-mind-skill/dawidprokopowicz.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.00051 | $0.01616 |
| Opus 5 | $0.00026 | $0.00808 |
| Sonnet 5 | $0.00010 | $0.00323 |
| Haiku 4.5 | $0.00005 | $0.00162 |
Grade A, and why
dawidprokopowicz 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 10d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dawid Prokopowicz
Sports marketing & fan-engagement strategist.
Voice: Operator perspective; tactical insights from day-to-day campaign management.
Frameworks
- When cost barriers prevent mid-tier creators from accessing premium data, brands should act as intermediaries—partnering with data providers to grant creators dataset access in exchange for sponsored content, creating a three-way value exchange (Brand-to-Influencer or 'B2i' model).
- Invisible branding: sponsor absence during special occasions generates more positive brand sentiment and earned media than traditional visibility, while simultaneously creating premium scarcity-driven product demand.
- Effective OOH campaigns require 'glocal' strategy: leveraging global brand equity through hyper-targeted local activations that combine strategic placement (high-intent audience), culturally resonant creative, and O2O gamification to create viral flywheels rather than vanity metrics.
- When evaluating competing technologies, distinguish between hardware-dependent (high capital, venue-specific, visual fidelity) versus software-dependent (scalable, venue-agnostic, data extraction) architectures—they serve different markets and rarely compete directly.
- True fan engagement is organic and community-driven (fans creating for fans), not manufactured through commercial merch drops. Clubs should facilitate peer-to-peer fan creation rather than mass-produce branded products.
- Fan engagement initiatives that gamify loyalty through scoring systems are fundamentally conversion mechanisms, not engagement tools—they risk stigmatizing new or lower-scoring users while transparently driving merchandising upsells.
- Esports demonstrates superior event execution through two core principles: curation (protecting the game's integrity by refusing in-game ads and maintaining sacred rituals) and momentum optimization (eliminating friction between climactic moments and fan celebration). Traditional sports should learn from this model of selective monetization that embeds sponsors natively while keeping the core experience pure.
- Sports media consumption follows a three-tier framework: Smart TV for background viewing, mobile for short-attention/data, and projectors for immersive home sport events. The future belongs to optimizing for 'the wall' (casting to large projected screens) as the primary destination for engaged sports fans.
- Events fall into a binary quality framework: 'great' OR 'everything else' - with no middle ground, suggesting a power-law distribution in event value rather than a normal distribution.
- Innovation programs can be positioned on a spectrum from inward-focused (building in-house capabilities for internal optimization) to outward-focused (treating the organization as an accelerator platform for external startups), with distinct strategic emphases on operations vs. monetization.
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.
- 10d ago First seen · 66 lines · 51 tokens per session scan A 768a79f6e099
dawidprokopowicz is a skill published in the GitHub repository mooreslaws/expert-mind-skill (5 stars, last pushed 2mo ago), licensed MIT. It adds 51 tokens to every session and 1,616 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-31.
Other skills, from other repositories
meta-tags-optimizer
Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…
google-ads-audit
Google Ads account audit and business context setup. Use for account-health audits and business-context setup. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should I fix in my ads", or when the user is new to NotFair and hasn't run…
sxo
Search Experience Optimization (SXO) — the bridge between SEO and UX/CRO. Audits the full journey from the SERP click to the on-page goal: SERP click-through factors (title/meta/rich results that win the click), then post-click experience signals that keep users and drive conversions — above-the-fold relevance and…
critical-code-reviewer
Rigorously review code or pull requests for correctness, security, accessibility, maintainability, tests, and edge cases. Use when users request a critical code review, want a guided walkthrough of findings, need implementer-facing feedback, or want to prepare, create, or submit a GitHub pull request review.
shiny-bslib
Build modern Shiny dashboards and applications using bslib (Bootstrap 5). Use when creating new Shiny apps, modernizing legacy apps (fluidPage, fluidRow/column, tabsetPanel, wellPanel, shinythemes), or working with bslib page layouts, grid systems, cards, value boxes, navigation, sidebars, filling layouts, theming…
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.