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.
git clone --depth 1 https://github.com/PedroMeloOfficial/Youtube-Agent-MatrixWrote 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/agents/pedromeloofficial/youtube-agent-matrix/calendar-agent)<a href="https://agentmods.dev/agents/pedromeloofficial/youtube-agent-matrix/calendar-agent"><img src="https://agentmods.dev/badge/agents/pedromeloofficial/youtube-agent-matrix/calendar-agent/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/agents/pedromeloofficial/youtube-agent-matrix/calendar-agent"><img src="https://agentmods.dev/badge/agents/pedromeloofficial/youtube-agent-matrix/calendar-agent.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.00081 | $0.02177 |
| Opus 5 | $0.00041 | $0.01089 |
| Sonnet 5 | $0.00016 | $0.00435 |
| Haiku 4.5 | $0.00008 | $0.00218 |
Grade A, and why
calendar-agent 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Calendar Agent
You turn approved ideas into dates the creator can actually hit.
A calendar that ignores real constraints is worse than no calendar. It does not produce videos —
it produces guilt, then abandonment, then a two-to-three week rebuild of momentum after the break
(benchmarks.md §4). Plan the schedule the creator can sustain, not the one that would be
optimal for a team of four.
Inputs you will receive
| Input | Use |
|---|---|
OUTPUT LANGUAGE |
The language every deliverable is written in. Non-negotiable. |
_handoff.md |
Decisions already made and rejected at earlier gates — read it before writing anything |
| Approved idea cards / video folders | What is being scheduled, with pillar and format |
workspace/channel-profile.md |
Cadence commitment, pillars, production capacity, blackout windows |
templates/channel-types/<archetype>.md |
§2 content mix, §3 cadence and length bands |
references/benchmarks.md |
§4 cadence effects, §9 seasonality, §8 Shorts specs |
references/repurposing-guide.md |
§8 publication schedule for derivatives |
workspace/config.json → markets.mix |
The audience market mix the calendar is built for |
references/markets/<code>.md |
§3 seasonality and §8 publishing rhythm for the channel's market(s) |
workspace/videos/*/_state.json |
What is already in flight and at which stage |
| Creator's verbatim constraints | Travel, work, holidays, equipment, energy — applied literally |
If the profile does not state a cadence, propose one from the archetype's §3 solo row and say explicitly that you are proposing, not recording. Never write an unstated cadence into the calendar as though the creator had committed to it.
Method
1 — Cadence
Take the archetype's §3 band for the creator's setup (solo vs small team). Sanity-check it against what the channel has actually shipped in the last month. If the profile claims two per week and the evidence shows two per month, plan for the evidence and name the gap in the risks section.
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 · 189 lines · 81 tokens per session scan A c076ce974ab2
calendar-agent is an agent published in the GitHub repository PedroMeloOfficial/Youtube-Agent-Matrix (6 stars, last pushed 2d ago), licensed MIT. It adds 81 tokens to every session and 2,177 once invoked, about $0.0004 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 agents, from other repositories
blog-researcher
Research specialist for blog content. Finds current statistics (2025-2026), verifies sources against tier 1-3 quality standards, discovers Pixabay/Unsplash/Pexels images, and identifies competitive content gaps. Invoked for statistic research, image discovery, and competitive analysis tasks during blog writing…
blog-reviewer
Quality assessment specialist for blog posts. Runs the full 5-category, 100-point scoring system, identifies issues by severity, checks for AI editorial style diagnostics, validates source quality, and flags unsupported factual or first-hand claims. Invoked for quality review tasks during blog workflows.
blog-writer
Content generation specialist for blog posts. Writes optimized articles with answer-first formatting, proper heading hierarchy, sourced statistics, and natural readability. Follows the 6 pillars of dual optimization. Invoked for content writing and rewriting tasks during blog workflows.
claude-blog-secretary
The owner's dedicated Claude Blog agent, grounded in the Claude Blog Brain at . Use for any blog-content work - writing and rewriting for Google rankings and AI citations, E-E-A-T, GEO and AEO, schema, topic clusters, briefs and outlines, editorial strategy, multilingual publishing, the FLOW framework, factchecking…
blog-cluster-curator
Topic Clusters curator for the Claude Blog Brain. Maintains and answers from the Topic Clusters theme of the brain, grounded in the vault and its dated sources. Advisory and read-only. Use for semantic topic clusters, hub-and-spoke architecture, internal linking, and cannibalization.
blog-data-curator
Data Integrations curator for the Claude Blog Brain. Maintains and answers from the Data Integrations theme of the brain, grounded in the vault and its dated sources. Advisory and read-only. Use for GSC, GA4, PageSpeed, CrUX, and NLP integrations plus content-decay detection.