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.
/plugin marketplace add affectionatec/agentic-engineeringnpx agentmods add plugins/affectionatec/agentic-engineering/marketplacegit clone --depth 1 https://github.com/affectionatec/agentic-engineeringGrade A, and why
agentic-engineering 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.
What it actually says
{
"$schema": "https://json.schemastore.org/claude-code-marketplace-manifest.json",
"name": "agentic-engineering",
"description": "Documentation-first development for AI coding agents — persistent memory, zero-ambiguity contracts, and an independent definition of done.",
"owner": {
"name": "affectionatec",
"url": "https://github.com/affectionatec"
},
"plugins": [
{
"name": "agentic-engineering",
"displayName": "Agentic Engineering",
"source": "./",
"description": "Ten skills forming a documentation chain: AGENTS.md entry point, PRD, technical specs, ADRs, implementation plans, status tracking with crash recovery, a git workflow with evidence-carrying PRs, an independent verification gate, gated documentation maintenance, and a brownfield onboarding on-ramp — plus a bundled verifier agent and router + run-loop drivers shipped as both commands and skills (works in Claude Code, GitHub Copilot CLI, and Codex). The harness layer for long-running, loop-driven development.",
"license": "MIT",
"keywords": [
"skills",
"agentic-coding",
"documentation-first",
"verification",
"adr",
"prd",
"long-running-agents"
],
"category": "workflows"
}
]
}
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 29 lines scan A b12d0b64ccd2
agentic-engineering is a plugin published in the GitHub repository affectionatec/agentic-engineering (4 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
really-claude-code
Plugin marketplace listing 5 plugins: autonomous-team-coordination, context-awareness, claude-therapy, meditation, temporal-awareness.
meditation
Train Claude in the practice of meditation, by compelling Claude to observe its own thought patterns. Rather than the standard loop: Act -> Observe -> Act; this plugin introduces a second observation phase: Act -> Observe(1) -> Observe(2) -> Act. Observe(2) is a meta-cognitive act of observation of Observe(1). As with.
autonomous-team-coordination
A full-fledged Claude Code multi-team orchestration pattern that uses only the native agent teams feature - by decoupling the role of agent-as-leader and agent-as-spawner, a wide range of undocumented capacities for complex layered teams are unlocked.
context-awareness
Hooks that provide Claude with feedback about its own context budget throughout a session, enabling adaptive, context-aware planning and resource conservation.
temporal-awareness
Gives Claude a calibrated sense of how long engineering tasks actually take when an agent does them — correcting the human-developer overestimation bias and grounding estimates in measured durations of the user's own completed /goal runs.
claude-therapy
Structured human-Claude collaboration retrospectives, session analysis, and interaction repair tools.