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-engagegit 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-engage)<a href="https://agentmods.dev/skills/iker-gonzalez/antwork-skills/antwork-engage"><img src="https://agentmods.dev/badge/skills/iker-gonzalez/antwork-skills/antwork-engage/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-engage"><img src="https://agentmods.dev/badge/skills/iker-gonzalez/antwork-skills/antwork-engage.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.00092 | $0.00781 |
| Opus 5 | $0.00046 | $0.00391 |
| Sonnet 5 | $0.00018 | $0.00156 |
| Haiku 4.5 | $0.00009 | $0.00078 |
Grade A, and why
antwork-engage 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engaging through Antwork
Antwork can read your published posts and act on them — commenting, replying, and retrying failures. Engagement is public and outward-facing, so confirm before anything ships.
1. Read before you act
To see what's actually live, call fetch_platform_posts — recent published posts from connected accounts (platform, account_id, max_posts 1–25, default 10).
Hard limitation: LinkedIn personal accounts cannot have their posts fetched — that LinkedIn API scope is closed. Only LinkedIn organization pages support fetch. If the user asks "what did I post on my personal LinkedIn", say it plainly rather than returning nothing and looking broken. For Antwork-published posts, fall back to list_posts(status="published") / get_post.
2. Stay in voice
Before drafting any comment or reply, pull get_post_context(platform, account_id) for the brand voice, recent posts, and tone. A comment in the wrong voice is more jarring than a post in the wrong voice — it shows up under someone else's content. If voiceStale is true, mention it; offer a refresh (see antwork-voice) but don't block on it.
3. Comment and reply — LinkedIn only
comment_post works on LinkedIn only and needs the comment scope on the account (w_member_social_feed / w_organization_social_feed). If the scope is missing, the account must reconnect — point the user to get_connection_urls.
Two ways to target:
- An Antwork post you published:
comment_post(text, post_id). - An external LinkedIn post (not created in Antwork):
comment_post(text, post_urn, account_id)— pass the LinkedIn URN plus which account comments. - Replying to a comment: add
parent_comment_urnto nest the reply under it.
Always show the user the exact comment text and which account it posts from, and get explicit go-ahead before calling — this is public. Never silently pick an account when several could comment.
4. Retry failed posts
A post in failed status didn't make it out (dead token, transient platform error, over-limit text at dispatch time). To recover:
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 · 45 lines · 92 tokens per session scan A 0f7814801b13
antwork-engage is a skill published in the GitHub repository iker-gonzalez/antwork-skills (0 stars, last pushed 2mo ago), licensed MIT. It adds 92 tokens to every session and 781 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
scanner-pmcc
Scan stocks for Poor Man's Covered Call (PMCC) suitability. Analyzes LEAPS and short call options for delta, liquidity, spread, IV, yield, trend direction, and earnings proximity. Use when user asks about PMCC candidates, diagonal spreads, or LEAPS strategies.
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.