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/adologyai/content-intelligence-plugin/weekly-briefnpx skills add adologyai/content-intelligence-plugin --skill weekly-briefgit clone --depth 1 https://github.com/adologyai/content-intelligence-pluginWrote 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/adologyai/content-intelligence-plugin/weekly-brief)<a href="https://agentmods.dev/skills/adologyai/content-intelligence-plugin/weekly-brief"><img src="https://agentmods.dev/badge/skills/adologyai/content-intelligence-plugin/weekly-brief.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.00170 | $0.05968 |
| Opus 5 | $0.00085 | $0.02984 |
| Sonnet 5 | $0.00034 | $0.01194 |
| Haiku 4.5 | $0.00017 | $0.00597 |
Grade A, and why
weekly-brief scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
> `requests` can be blocked in some sandboxes the same way `curl` is), How it starts
The opening of the file, as written. The whole thing — 453 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Weekly Competitive Intelligence Brief
Build a polished 3-page PDF competitive intelligence report from an Adology project's scope. Each page is a self-contained "slide" with its own data pipeline, rendered as HTML via WeasyPrint, then merged into a single PDF. Every page includes real post thumbnails.
Architecture Rules
DO NOT use subagents. Build all 3 pages yourself, sequentially, in the main thread. Subagents caused cascading failures in production — they made unchecked decisions, crashed the sandbox disk, and couldn't be course-corrected.
Thumbnails are MANDATORY. Every scoreboard card, spotlight, trend card, and coaching
card must have a real thumbnail image from the actual post. The skill includes a bundled
script (scripts/download_thumbnails.py) that handles downloading, resizing, and
base64-encoding. You run this script — it produces a JSON file mapping image URLs to
small base64 data URIs. Then you insert those data URIs into the HTML <img> tags.
There is no alternative to this. Do not skip thumbnails. Do not use CSS placeholders.
Do not use colored rectangles with initials. Download the real images.
Coverage is part of the brief, not a caveat you drop. A weekly brief is a claim about a window. Say which sources actually cover that window and name the ones that don't — by name, on the page. A stale source that goes unmentioned turns a data gap into a false finding ("Brand X went quiet this week" when nobody fetched Brand X).
Path Conventions
This skill's shell examples use two literal placeholders that you must substitute before running any command:
{skill_path}— the absolute path to this skill's directory (the directory containing thisSKILL.md). At runtime this resolves to something like/Users/<you>/.../skills/weekly-brief. Use it to invoke bundled scripts underscripts/and to read reference files underreferences/.{output_dir}— the working/output directory for this brief's HTML, JSON, and final PDF artifacts. Pick a fresh directory per run (e.g.outputs/<project_name>-<week_end>/) and substitute it consistently across the whole workflow.
What ships with it
12 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.
- references/P1_output_schema.yaml 8.0 KB
- references/P1_prompt.txt 8.9 KB
- references/P1_render_package.html 15 KB
- references/P2_output_schema.yaml 9.2 KB
- references/P2_prompt.txt 7.3 KB
- references/P2_render_package.html 15 KB
- references/P3_output_schema.yaml 9.3 KB
- references/P3_prompt.txt 6.6 KB
- references/P3_render_package.html 12 KB
- scripts/assemble_pdf.py 7.0 KB runs code
- scripts/download_thumbnails.py 6.8 KB runs code
- scripts/qa_check.py 15 KB runs code
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.
- 5d ago First seen · 453 lines · 170 tokens per session scan A afe8622bdf63
weekly-brief is a skill published in the GitHub repository adologyai/content-intelligence-plugin (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 170 tokens to every session and 5,968 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…