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 iker-gonzalez/antwork-skills --skill antwork-calendargit clone --depth 1 https://github.com/iker-gonzalez/antwork-skillsWrote 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/iker-gonzalez/antwork-skills/antwork-calendar)<a href="https://agentmods.dev/skills/iker-gonzalez/antwork-skills/antwork-calendar"><img src="https://agentmods.dev/badge/skills/iker-gonzalez/antwork-skills/antwork-calendar/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/iker-gonzalez/antwork-skills/antwork-calendar"><img src="https://agentmods.dev/badge/skills/iker-gonzalez/antwork-skills/antwork-calendar.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.00097 | $0.01084 |
| Opus 5 | $0.00048 | $0.00542 |
| Sonnet 5 | $0.00019 | $0.00217 |
| Haiku 4.5 | $0.00010 | $0.00108 |
Grade A, and why
antwork-calendar 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planning a content calendar with Antwork
Antwork is an MCP-native social scheduler. A calendar is just a set of drafts each bound to one account and a scheduled_for time. The job is to plan the whole grid first, get approval, then create and schedule each slot. This workflow codifies the mistakes assistants make when batch-scheduling.
1. Read the existing calendar before proposing anything
Never schedule into a vacuum. First call:
get_calendar(date_from, date_to)— what's already scheduled or published in the target window. Plan around it; don't double-book a slot or repeat a topic that just went out.get_optimal_posting_times— the workspace's configured posting times and timezone, plus which accounts are selected per platform. These times are your default slots.list_social_accounts— the accounts you can target (withaccount_id, platform, handle, token health). Skip accounts whosetokenHealthStatusisn'thealthy— flag them for reconnect instead of scheduling onto a dead token.
If multiple workspaces exist and none is default, resolve with set_default_workspace before anything else.
2. Present the calendar as a plan — and wait
Editing a plan is cheaper than editing fifteen drafts. Present the calendar as a numbered table and stop for explicit approval before creating a single post. One row per slot:
# | date · time (tz) | account / platform | hook | goal
Use templates/content-calendar.md as the skeleton. Space slots across the get_optimal_posting_times windows — don't stack three posts at 09:00. Respect per-platform cadence norms (X tolerates several a day; LinkedIn one a day is plenty). Vary topics and formats across the week so the feed doesn't read as repetitive.
Do not call create_post during planning.
3. Draft in the account's voice, per slot
Once approved, work slot by slot. For each row, before writing copy:
get_post_context(platform, account_id)— pulls brand, the account's voice profile, recent posts, and avoiceStaleflag. Match that voice; don't impose a house style. IfvoiceStaleis true, mention it and offer to refresh via theantwork-voiceskill before drafting a whole week in a stale voice.
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 · 60 lines · 97 tokens per session scan A 14cdc3b65323
antwork-calendar is a skill published in the GitHub repository iker-gonzalez/antwork-skills (0 stars, last pushed 2mo ago), licensed MIT. It adds 97 tokens to every session and 1,084 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-08-31.
Other skills, from other repositories
ib-trailing-stop
Server-side trailing stop management for stocks and naked LEAPS in IB. Places native TRAIL orders that auto-ratchet the stop as price climbs. Dry-run by default. Requires TWS or IB Gateway running locally.
ib-trades-history
Fetch trade executions from Interactive Brokers filtered by account, date range, or symbol. Supports live API (7 days history) and FlexReport (full history). Use when user asks about their trades, executions, or transaction history. Requires TWS or IB Gateway running locally.
fundamentals
Get fundamental financial data including financials, earnings, and key metrics. Use when user asks about financials, earnings, revenue, profit, balance sheet, income statement, or company fundamentals.
ib-collar
Generate tactical collar strategy reports for protecting PMCC positions through earnings or high-risk events. Requires TWS or IB Gateway running locally.
ib-portfolio-action-report
Generate a comprehensive portfolio action report with earnings dates and risk assessment. Use when user asks for portfolio review, action items, earnings risk, or position management across IB accounts. Requires TWS or IB Gateway running locally.
report-stock
Generate comprehensive stock analysis report (PDF or markdown) with trend, PMCC, and fundamental analysis.