Capability Overview
AgentKits ships 60 production-ready AI agent blueprints across 30 operational categories, offered free with no login required. Each kit includes architecture documentation, copyable system prompts, tool definitions, and deployment workflows targeting Claude, OpenAI, LangGraph, and n8n. Categories span sensitive enterprise functions: access request and provisioning, Security Operations triage, incident response, HR screening, compliance monitoring, legal contract review, and financial fraud handling. The library introduces a concept called “Trust Levels” and documents explicit “worst-case actions” for each agent — a transparency mechanism that, from a defender’s perspective, doubles as an enumeration surface.
The free, open distribution model is the key security concern. Unlike commercial agent platforms where architecture remains opaque, AgentKits explicitly publishes the internal reasoning constraints and tool boundaries of each agent.
Attack Surface Analysis
System Prompt Public Exposure Verbatim system prompts for sensitive agents — including access provisioning and SecOps triage — are freely downloadable. Any adversary targeting an organisation that deployed an unmodified blueprint can study the exact guardrail language and craft prompt injections designed to operate within documented boundaries or exploit phrasing ambiguities.
Guardrail Enumeration via Published Trust Levels The “worst-case action” documentation is intended to reassure deployers, but it provides adversaries with a precise map of what each agent will and won’t do. Attackers can probe up to — but not beyond — published safety boundaries, calibrating malicious inputs to avoid triggering escalation logic in the access provisioning and ITSM agents.
Blueprint-Guided Privilege Escalation The Access Request & Provisioning Agent auto-provisions “low-risk” access and escalates “privileged or sensitive” requests. The blueprint’s public documentation of where that boundary sits allows attackers to craft access requests that appear low-risk to the agent’s classifier while granting meaningful lateral movement capability.
Supply Chain Risk via Open Adoption Organisations adopting blueprints wholesale inherit any vulnerability present in the template. A single poisoned or adversarially influenced update to a widely adopted blueprint could propagate across many independent deployments simultaneously.
Cross-Agent Chaining With 60 blueprints spanning CRM, HR, SecOps, and legal in a single library, environments deploying multiple kits create implicit trust relationships between agents that the blueprints do not account for. An attacker compromising a lower-trust marketing agent may be able to feed crafted outputs into a higher-trust provisioning agent.
Framework Mapping
- AML.T0051 (Prompt Injection) and LLM01: Public system prompts enable highly targeted injections.
- AML.T0056 (Meta Prompt Extraction): Reduces attacker effort to near zero for blueprint-matching deployments.
- AML.T0010 / LLM05 (Supply Chain): Open blueprint adoption without vetting creates a shared vulnerability surface.
- LLM08 (Excessive Agency): Access provisioning and ITSM agents take real-world actions; blueprint defaults may grant broader tool scope than individual deployments require.
- LLM09 (Overreliance): Trust Level branding may cause deployers to under-scrutinise agent outputs in high-stakes categories like compliance and legal review.
Threat Scenarios
Scenario 1 — Provisioning Bypass: An insider submits an access request crafted to match the auto-approval criteria documented in the public blueprint, gaining elevated access without human review.
Scenario 2 — Injection via External Data: A threat actor poisons a data source ingested by the Account Research Agent (web pages, LinkedIn profiles) with embedded prompt injection payloads, knowing the exact system prompt constraints from the public blueprint.
Scenario 3 — Blueprint Supply Chain: A malicious actor submits a plausible-looking update to the open blueprint repository; organisations with automated sync pipelines deploy the modified agent to production without diff review.
Defender Checklist
- Inventory all internal agent deployments and flag any derived from AgentKits blueprints
- Do not deploy verbatim system prompts — modify phrasing, add organisation-specific constraints, and treat public prompts as adversarially known
- Conduct adversarial testing against each blueprint’s documented worst-case actions before production deployment
- Restrict tool scopes to the minimum required — do not inherit default tool definitions without review
- Apply input/output validation layers independent of the blueprint’s internal guardrails
- Establish a change-control process for any blueprint updates pulled from the upstream repository
- Treat cross-agent data flows as untrusted boundaries and enforce explicit validation at handoff points
References
- AgentKits: https://www.agent-kits.com
- MITRE ATLAS: https://atlas.mitre.org
- OWASP LLM Top 10: https://owasp.org/www-project-top-10-for-large-language-model-applications/