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 mcp/johnisanerd/apify-linkedin-posts-api/linkedin-postsgit clone --depth 1 https://github.com/johnisanerd/Apify-LinkedIn-Posts-APIGrade A, and why
linkedin-posts 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 yesterday.
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- yesterday First seen · 6 lines scan A aca9ac3b62d8
linkedin-posts is an MCP server published in the GitHub repository johnisanerd/Apify-LinkedIn-Posts-API (0 stars, last pushed 3d ago), with no licence file. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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 mcp servers, from other repositories
apify-store-api-example
MCP server "apify-store-api-example" as configured in johnisanerd/Apify-Store-API. Runs locally from the apify-store-api-example Python package.
apify-linkedin-company-api
MCP server "apify-linkedin-company-api" as configured in johnisanerd/Apify-LinkedIn-Company-API. Runs locally from the apify-linkedin-company-api Python package.
apify-jazzhr-jobs-api
MCP server "apify-jazzhr-jobs-api" as configured in johnisanerd/Apify-JazzHR-Jobs-API. Runs locally from the apify-jazzhr-jobs-api Python package.
apify-n8n-templates-api-example
MCP server "apify-n8n-templates-api-example" as configured in johnisanerd/Apify-N8n-Templates-API. Runs locally from the apify-n8n-templates-api-example Python package.
apify-icims-careers-api-example
MCP server "apify-icims-careers-api-example" as configured in johnisanerd/Apify-iCIMS-Careers-API. Runs locally from the apify-icims-careers-api-example Python package.
skyvern
AI-powered browser automation — navigate, click, fill forms, and extract data from any website. Remote server at api.skyvern.com.