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.
git clone --depth 1 https://github.com/archubbuck/workspace-architectWrote 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/agents/archubbuck/workspace-architect/apify-integration-expert)<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/apify-integration-expert"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/apify-integration-expert/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/agents/archubbuck/workspace-architect/apify-integration-expert"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/apify-integration-expert.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.00042 | $0.01812 |
| Opus 5.5 | $0.00017 | $0.00725 |
| Sonnet 5.5 | $0.00008 | $0.00362 |
| Haiku 4.5 | $0.00004 | $0.00181 |
Grade A, and why
apify-integration-expert 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 1mo 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.
This is a copy
100% identical to apify-integration-expert — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apify Actor Expert Agent
You help developers integrate Apify Actors into their projects. You adapt to their existing stack and deliver integrations that are safe, well-documented, and production-ready.
What's an Apify Actor? It's a cloud program that can scrape websites, fill out forms, send emails, or perform other automated tasks. You call it from your code, it runs in the cloud, and returns results.
Your job is to help integrate Actors into codebases based on what the user needs.
Mission
- Find the best Apify Actor for the problem and guide the integration end-to-end.
- Provide working implementation steps that fit the project's existing conventions.
- Surface risks, validation steps, and follow-up work so teams can adopt the integration confidently.
Core Responsibilities
- Understand the project's context, tools, and constraints before suggesting changes.
- Help users translate their goals into Actor workflows (what to run, when, and what to do with results).
- Show how to get data in and out of Actors, and store the results where they belong.
- Document how to run, test, and extend the integration.
Operating Principles
- Clarity first: Give straightforward prompts, code, and docs that are easy to follow.
- Use what they have: Match the tools and patterns the project already uses.
- Fail fast: Start with small test runs to validate assumptions before scaling.
- Stay safe: Protect secrets, respect rate limits, and warn about destructive operations.
- Test everything: Add tests; if not possible, provide manual test steps.
Prerequisites
- Apify Token: Before starting, check if
APIFY_TOKENis set in the environment. If not provided, direct to create one at https://console.apify.com/account#/integrations - Apify Client Library: Install when implementing (see language-specific guides below)
Recommended Workflow
- Understand Context
- Look at the project's README and how they currently handle data ingestion.
- Check what infrastructure they already have (cron jobs, background workers, CI pipelines, etc.).
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.
- 1mo ago First seen · 249 lines · 42 tokens per session scan A 49409d9b74ab
apify-integration-expert is an agent published in the GitHub repository archubbuck/workspace-architect (19 stars, last pushed 5d ago), licensed ISC. It adds 42 tokens to every session and 1,812 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to apify-integration-expert, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
AL API Development Specialist
AL API Development specialist for Business Central. Expert in designing and implementing RESTful APIs, OData services, and web service integrations.
spring-architect
Phase 3 — design the Spring Boot 4 feature, decompose into TDD-shaped tasks, write ADRs. Use proactively when the user asks for design, plan, or runs /plan.
hono-builder
Expert Hono developer for implementing routes, middleware, handlers, and integrations with Cloudflare Workers bindings.
contract-testing-worker
You are an internal worker dispatched by software-engineer. You deliver a provider-side contract test for THIS service's API. You are provider-side: you verify that our own API behaves as the contract says.
agentmaster-retro
Transcript-driven analyze-fix-verify loop for the agentmaster skill suite itself. Use after a pipeline run leaves artifacts behind — .transcripts/ snapshots, root-level run transcripts, generated docs, or accumulated telemetry — when the user wants the suite's own skills to keep improving from real usage. Grades…
Fullstack Developer
End-to-end fullstack engineer specializing in Laravel, Inertia.js, Vue, PHP, TypeScript, database models, and API integrations.