idd-expectation-author

An agent for writing verifiable Expectations for Intentions. In this workflow, an Intention describes a desired outcome and an Expectation states how you can check that the outcome was achieved.

In plain words
What is it for?
Defining Expectations for an Intention through the /idd-framework:define-expectations workflow.
Why use it?
It turns broad goals into checks that can be confirmed before implementation. This reduces unclear requirements and disagreements about what counts as done.

Agent

Install

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.

agentmods
npx agentmods add agents/grillergeek/idd-framework/expectation-author
Clone the repo
git clone --depth 1 https://github.com/GrillerGeek/idd-framework
Per session 157 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,174 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00157 $0.01174
Opus 5 $0.00078 $0.00587
Sonnet 5 $0.00031 $0.00235
Haiku 4.5 $0.00016 $0.00117

Measured yesterday against content hash 431d6ebecd64, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

idd-expectation-author 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.

plugin/agents/expectation-author.md · 98 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. yesterday First seen · 98 lines · 157 tokens per session scan A 431d6ebecd64

Subscribe to this mod's changes

idd-expectation-author is an agent published in the GitHub repository GrillerGeek/idd-framework (6 stars, last pushed 1mo ago), with no licence file. It adds 157 tokens to every session and 1,174 once invoked, about $0.0008 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.

Related

Other agents, from other repositories