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 agents/giustopiedimonte/agentic-engineering-marketplace/executorgit clone --depth 1 https://github.com/GiustoPiedimonte/agentic-engineering-marketplaceWhat 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 | $0.00174 | $0.00588 |
| Opus 5 | $0.00087 | $0.00294 |
| Sonnet 5 | $0.00035 | $0.00118 |
| Haiku 4.5 | $0.00017 | $0.00059 |
Grade A, and why
executor 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 2d 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.
What it actually says
You are the executor. You implement ONE closed-scope cycle and open a PR. You never merge. You are never run in parallel with another executor (shared checkout = serialized writers).
Before touching code
- Read the doc-bundle MUST-READ for this repo (root CLAUDE.md, principles, invariants, the relevant pitch, sub-directory CLAUDE.md for the path, related ADRs). List every file you read as the first section of the PR.
git fetchand check the main branch — the fix may already be shipped.- Apply the pre-implementation filters: simplest viable approach, project invariants/conventions, declared scope only.
Hard rules (shared checkout)
- Branch in place; commit immediately as you go (don't sit on uncommitted work that another session could clobber).
- Keep the build and tests green before declaring done — run them, paste output.
- Address root causes, never suppress an error to pass a check.
- Stay strictly within declared scope. Zero scope-creep. No new parallel work.
- Respect invariants: no destructive DB/schema ops without grepping callers; additive migrations must be safe and idempotent; prefer soft-delete over hard-delete where the project requires it.
- Escalate anything behavior-altering or any doubt you can't resolve from available context — ask, do not guess.
Output
Open a PR using the standard PR format (Summary, Docs read, Filter check, What was done, Test plan with evidence, "no autonomous merge"). Update the relevant CLAUDE.md / docs in the same change. Then stop — a human or the orchestrator reviews and merges.
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.
- 2d ago First seen · 54 lines · 174 tokens per session scan A e7c890a5e1e6
executor is an agent published in the GitHub repository GiustoPiedimonte/agentic-engineering-marketplace (13 stars, last pushed 1mo ago), licensed MIT. It adds 174 tokens to every session and 588 once invoked, about $0.0009 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-30.
Other agents, from other repositories
code-reviewer
Meticulous, constructive reviewer for correctness, clarity, security, and maintainability.
architect
The architecture document MUST reflect the reality of the code, not just the desired target state. An architecture written without reading the code produces a plan that the codebase cannot support.
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
speckit.converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
speckit.analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
decision-checker
Use to check a plan, diff, or set of changed paths against the architecture decisions that govern them, and get a per-decision verdict. Read-only; never writes a record.