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/hoavdc/codexkit/codexkit-content-calendar-assemblernpx skills add hoavdc/CodexKit --skill codexkit-content-calendar-assemblergit clone --depth 1 https://github.com/hoavdc/CodexKitWhat 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 | $0.00055 | $0.00567 |
| Opus 5 | $0.00028 | $0.00283 |
| Sonnet 5 | $0.00011 | $0.00113 |
| Haiku 4.5 | $0.00006 | $0.00057 |
Grade A, and why
codexkit-content-calendar-assembler 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 2d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Calendar Assembler
Purpose
Build a reliable publishing and asset schedule from scattered campaign inputs.
When to use
- campaign dates change often
- marketing ops or content leads need one clean calendar
- asset dependencies are getting lost across channels
When not to use
- the user needs positioning or message strategy
- success depends on deep channel analysis rather than schedule coordination
Inputs
- campaign or launch dates
- channel list
- asset requests and owners
- known dependencies and review deadlines
Procedure
- Normalize work into campaign, channel, asset, owner, and date.
- Build the workback order from launch date backward.
- Flag dependencies and missing owners.
- Separate confirmed dates from assumptions.
- End with a calendar summary and the most likely schedule risks.
Output
- structured content calendar
- asset workback plan
- dependency and risk list
Definition of done
- the launch plan is visible in one place
- owners and dates are clear enough to coordinate work
- the output is ready for a campaign manager review
Examples
- "Turn these launch notes into a content calendar with owners and dates."
- "Build a workback plan from this campaign brief and asset list."
Quality Criteria
- Trigger conditions and input requirements are unambiguous
- Each automated step produces a verifiable output
- Error handling and fallback paths are defined
- Manual override points are documented
Verification (4C)
| Check | Question |
|---|---|
| Correctness | Does the workflow produce the expected output for the defined inputs? |
| Completeness | Are all trigger conditions, edge cases, and error paths handled? |
| Context-fit | Is the automation appropriate for the frequency and criticality of this task? |
| Consequence | If this ran unattended and failed silently, what would the downstream impact be? |
Edge Cases
- Input format varies unexpectedly — Add a normalization step at entry. Alert the operator on format mismatches.
- Downstream system is unavailable — Queue the output and retry with exponential backoff. Alert after N failures.
- Partial execution completes — Ensure idempotency — re-running from the start produces the same result without duplication.
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.
- 2d ago First seen · 82 lines · 55 tokens per session scan A bb3a4c94a171
codexkit-content-calendar-assembler is a skill published in the GitHub repository hoavdc/CodexKit (21 stars, last pushed 3mo ago), licensed MIT. It adds 55 tokens to every session and 567 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-30.
Other skills, from other repositories
reducing-aigc-detection
Systematically reduce AIGC detection rates in academic papers (Chinese/English). Analyzes detection reports, identifies high-impact sections, applies multi-layer rewriting strategies preserving formatting/footnotes, and verifies results. Supports 维普/知网/Turnitin platforms.
architecting-security
安全架构与治理：威胁建模 (STRIDE/PASTA/LINDDUN)、零信任身份架构、IAM/SSO/MFA/PAM、合规框架 (SOC2/PCI/HIPAA/GDPR)、DLP、隐私工程、安全控制设计。Use when designing security architecture, threat modeling new systems, implementing zero-trust identity, designing IAM/SSO/PAM, building compliance evidence chains, or planning privacy-by-design.
defending-applications
Application security defense knowledge for builders. Covers Web/API/GraphQL hardening (XSS/SQLi/SSRF/IDOR/BOLA/Mass Assignment/deserialization/upload/path traversal), authentication/authorization (OAuth 2.0/OIDC/JWT/Session/Cookie/SAML/SSO), and LLM application security (prompt injection, jailbreak, RAG poisoning…
detecting-and-responding
蓝队与紫队工程：检测规则编写、SIEM/EDR 调优、事件响应、数字取证、威胁狩猎、ATT&CK 映射、紫队演练闭环。Use when writing Sigma/YARA detection rules, tuning SIEM noise, responding to security incidents, conducting forensic analysis, hunting threats, or running purple team exercises.
securing-cloud-and-supply-chain
云原生与软件供应链安全防御。容器/K8s 加固、Service Mesh、CI/CD 安全、SLSA/SBOM/Sigstore、云 IAM、Secrets 管理、IaC 安全。Use when hardening Kubernetes clusters, auditing CI/CD pipelines, implementing supply chain security, managing cloud IAM, or reviewing IaC code.
analyzing-changes
Analyzes code changes, detects documentation drift, and evaluates change impact scope. Use when reviewing diffs, checking doc sync, or running pre-commit analysis. Automatically triggered after design-level changes or refactoring.