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 rules/talm/eclincher-mcp-server/eclincher-toolsgit clone --depth 1 https://github.com/talm/eclincher-mcp-serverWrote 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/rules/talm/eclincher-mcp-server/eclincher-tools)<a href="https://agentmods.dev/rules/talm/eclincher-mcp-server/eclincher-tools"><img src="https://agentmods.dev/badge/rules/talm/eclincher-mcp-server/eclincher-tools.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.00036 | $0.01269 |
| Opus 5 | $0.00018 | $0.00634 |
| Sonnet 5 | $0.00007 | $0.00254 |
| Haiku 4.5 | $0.00004 | $0.00127 |
Grade A, and why
eclincher-tools 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 6d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Eclincher tools
Eclincher manages social media over MCP across 12+ social networks: Facebook, Instagram, X/Twitter, LinkedIn, TikTok, Pinterest, YouTube, Google Business Profile, WordPress, Reddit, and Threads. Auth is OAuth 2.0 (or a static x-eclincher-api-key header, already in mcp.json); all data is scoped to the authenticated account. Follow each tool's inputSchema for exact fields — the notes below cover the non-obvious parts.
Always resolve IDs first
- Call
list_brandsto get brands.brandIdis an opaque token — pass back exactly what the tool returns; never construct, parse, or guess it. - Call
list_accountswith thatbrandIdto get connected profile IDs and their networks. - Feed those exact IDs into publishing, inbox, and analytics calls.
Async jobs — poll for results
create_postreturns ajobId; pollget_post_statusuntil it completes before assuming a post went out.- Some analytics reports run async too; poll
get_analytics_job_statusbyjobId.
Profiles are passed differently per tool
create_post→profile: an array of profile IDs (string[]).get_builtin_report→profileIds: a single profile UUID (string).get_comparison_report,get_cross_channel_report→profileIds: pipe-delimited UUIDs, e.g.uuid1|uuid2(max 20).
Time is Unix seconds (not milliseconds)
Applies to create_post.scheduleTimes and list_inbox.startTime/endTime. Omit scheduleTimes to publish now; only schedule times in the future.
Publishing
create_post— schedule or publish; one call can target multiple networks at once (include every destination profile in theprofilearray).textmax 10,000 chars;image/videoare https URLs. Async → returns ajobId.get_scheduled_posts— find scheduled posts by filters (time range, profiles, post types, search); returns each post's attachments with S3 URLs.edit_post— edit a scheduled post. To keep existing attachments, pass them back fromget_scheduled_posts; you can add new image/video URLs or replace the video (one video supported).get_post_status— check an asynccreate_postjob byjobId.
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.
- 6d ago First seen · 64 lines · 36 tokens per session scan A d6e3419fac32
eclincher-tools is a cursor rule published in the GitHub repository talm/eclincher-mcp-server (6 stars, last pushed 12d ago), licensed MIT. It adds 36 tokens to every session and 1,269 once invoked, about $0.0002 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 cursor rules, from other repositories
typescript
TypeScript best practices and coding standards.
auto-commit
Commit changes after every completed agent task.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.