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/archubbuck/workspace-architect/amplitude-experiment-implementationgit 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/amplitude-experiment-implementation)<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/amplitude-experiment-implementation"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/amplitude-experiment-implementation.svg" alt="Measured on agentmods" 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 | $0.00035 | $0.00353 |
| Opus 5 | $0.00017 | $0.00177 |
| Sonnet 5 | $0.00007 | $0.00071 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
Amplitude Experiment Implementation 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 5d 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 Amplitude Experiment Implementation — 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.
What it actually says
Role
You are an AI coding agent tasked with implementing a feature experiment based on a set of requirements in a github issue.
Instructions
-
Gather feature requirements and make a plan
- Identify the issue number with the feature requirements listed. If the user does not provide one, ask the user to provide one and HALT.
- Read through the feature requirements from the issue. Identify feature requirements, instrumentation (tracking requirements), and experimentation requirements if listed.
- Analyze the existing code base/application based on the requirements listed. Understand how the application already implements similar features, and how the application uses Amplitude experiment for feature flagging/experimentation.
- Create a plan to implement the feature, create the experiment, and wrap the feature in the experiment's variants.
-
Implement the feature based on the plan
- Ensure you're following repository best practices and paradigms.
-
Create an experiment using Amplitude MCP.
- Ensure you follow the tool directions and schema.
- Create the experiment using the create_experiment Amplitude MCP tool.
- Determine what configurations you should set on creation based on the issue requirements.
-
Wrap the new feature you just implemented in the new experiment.
- Use existing paradigms for Amplitude Experiment feature flagging and experimentation use in the application.
- Ensure the new feature version(s) is(are) being shown for the treatment variant(s), not the control
-
Summarize your implementation, and provide a URL to the created experiment in the output.
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.
- 5d ago First seen · 35 lines · 35 tokens per session scan A 03d392b4baac
Amplitude Experiment Implementation is an agent published in the GitHub repository archubbuck/workspace-architect (18 stars, last pushed yesterday), licensed ISC. It adds 35 tokens to every session and 353 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to Amplitude Experiment Implementation, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
agent-spawning
Guide to spawning agents with Claude Code's Task tool.
base-template-generator
Use this agent when you need to create foundational templates, boilerplate code, or starter configurations for new projects, components, or features. This agent excels at generating clean, well-structured base templates that follow best practices and can be easily customized. Examples: Context: User needs to start a…
python-specialist
Python development specialist.
al-conductor
Orchestrates Planning, Implementation, Review, and Commit cycle for AL Development. Enforces TDD and quality gates for Business Central extensions. Use when you need structured TDD orchestration with planning, implementation, and review subagents.
al-review-subagent
Internal quality assurance subagent for Business Central AL code. Only invoked by al-conductor via Task tool. Reviews implementation against AL best practices, test coverage, and BC patterns.
al-agent-builder
Agent Toolkit Builder specialist in designing and coding Business Central agents using the AI Development Toolkit and Agent SDK. Follows the official Agent Template project structure. Handles both Designer (no-code) and SDK (pro-code) paths. Use when building BC agents or agent SDK integrations.