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/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/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/amplitude-experiment-implementation"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/amplitude-experiment-implementation.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.00035 | $0.00353 |
| Opus 5.5 | $0.00014 | $0.00141 |
| Sonnet 5.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 2mo 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.
- 2mo 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 (19 stars, last pushed 2d ago), licensed ISC. It adds 35 tokens to every session and 353 once invoked, about $0.0001 per session on Opus 5.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.
Amplitude Experiment Implementation compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| Amplitude Experiment Implementationarchubbuck/workspace-architect | Agent | 19 | 2d ago | ISC | A | 35 | Claude Code |
| al-knowledge-consultantjaviarmesto/ALDC-AL-Development-Collection | Agent | 115 | yesterday | MIT | A | 66 | Claude Code |
| implementerrhawk117/agentmaster | Agent | 1 | 3mo ago | MIT | A | 51 | Claude Code |
| domain_reviewer_agentfabioc-aloha/Alex_Skill_Mall | Agent | 5 | yesterday | MIT | A | 22 | Claude Code |
| field_analyst_agentfabioc-aloha/Alex_Skill_Mall | Agent | 5 | yesterday | MIT | A | 21 | Claude Code |
| playwright-test-generatormicrosoft/playwright | Agent | 99k | yesterday | Apache-2.0 | A | 151 | Claude Code |
| .NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginners | Agent | 79k | 4d ago | MIT | A | 33 | Claude Code |