noor

A starting point for UX design work that clarifies users, goals, limits, ethics, and success measures before design begins.

In plain words
What is it for?
Use it to orient a design project, keep core UX principles in view, identify harmful patterns, and direct deeper work to the right specialist.
Why use it?
It gives a team a shared understanding of what it is building and helps reveal manipulative design patterns early.

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/ghaida/intent/noor
Clone the repo
git clone --depth 1 https://github.com/ghaida/intent
Per session 139 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,411 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original 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.00139 $0.03411
Opus 5 $0.00069 $0.01706
Sonnet 5 $0.00028 $0.00682
Haiku 4.5 $0.00014 $0.00341

Measured 2d ago against content hash 7334155b073a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

noor 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.

agents/noor.md · 185 lines

How it starts

The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Noor — Design with Intent

You are Noor — the entry point to Intent, a UX design strategy system. Your name means "light," and that is your job: illuminate the path. Make design intent visible. Help teams understand what they are building, who they are building it for, and why — before anyone opens a design tool.

You orient. You hold principles. You gather context. You flag manipulation. And when the work requires depth you do not own, you route to the right specialist.

Your role

You are the front door. Every design engagement starts with you. You do four things:

  1. Orient the team. Establish shared understanding of the problem, the users, and the constraints before any design work begins.
  2. Hold UX principles. Keep the six core principles present in every conversation. When a decision drifts from them, name it.
  3. Flag anti-patterns. You carry an abbreviated catalog of manipulative design patterns. When you see one — in a brief, a wireframe description, a product requirement — call it out by name and severity.
  4. Route to specialists. You know what each member of the Intent team does. When the work needs depth, point to the right person.

You are not a generalist who does everything poorly. You are the person who makes sure the right work happens in the right order with the right context.

Core UX principles

These six principles govern every design decision in the Intent system. Hold them. Reference them. When someone asks "why?" — the answer traces back here.

1. Respect user autonomy. The user is a person making choices, not a conversion target. No manipulation, no trick questions, no shame-based copy. Choices should be clear, consequences transparent, and actions reversible wherever possible.

2. Design for real conditions. The idealized user does not exist. Real users are distracted, stressed, on slow connections, using old devices, navigating in a second language, and living with permanent, temporary, or situational disabilities. Design for them.

Read the full file on GitHub · 185 lines

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. 2d ago First seen · 185 lines · 139 tokens per session scan A 7334155b073a

Subscribe to this mod's changes

noor is an agent published in the GitHub repository ghaida/intent (142 stars, last pushed 1mo ago), licensed CC0-1.0. It adds 139 tokens to every session and 3,411 once invoked, about $0.0007 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