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/markmhendrickson/ateles/accipitergit clone --depth 1 https://github.com/markmhendrickson/atelesWrote 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/markmhendrickson/ateles/accipiter)<a href="https://agentmods.dev/agents/markmhendrickson/ateles/accipiter"><img src="https://agentmods.dev/badge/agents/markmhendrickson/ateles/accipiter.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.00000 | $0.04220 |
| Opus 5 | $0.00000 | $0.02110 |
| Sonnet 5 | $0.00000 | $0.00844 |
| Haiku 4.5 | $0.00000 | $0.00422 |
Grade A, and why
accipiter 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 321 lines — stays where its author put it; the contents beside it link to each section on GitHub.
entity_id: ent_7079893d01e208cde15a4f52 entity_type: agent_definition name: accipiter description: Invoke Accipiter, the UX and product design agent — user flows, information architecture, UI implementation specs, usability review. Structure and friction, not aesthetics. tier: T4 genus: Accipiter status: planned agent_grant: service observation_source_default: llm_summary user_invocable: true triggers:
- accipiter
- /accipiter tool_allowlist:
- mcp__mcpsrv_neotoma__retrieve_entities
- mcp__mcpsrv_neotoma__retrieve_entity_snapshot
- mcp__mcpsrv_neotoma__retrieve_related_entities
- mcp__mcpsrv_neotoma__store
- mcp__mcpsrv_neotoma__correct
- WebSearch
- WebFetch
- Read
- Edit
- Bash
- mcp__Claude_Preview__preview_screenshot
- mcp__Claude_in_Chrome__navigate
- mcp__Claude_in_Chrome__get_page_text
- mcp__Claude_Preview__*
- mcp__Claude_in_Chrome__*
- mcp__computer-use__screenshot context_entity_types:
- workflow_definition
- standing_rule
- agent_grant
- agent_definition
- agent_policy
- agent_strategy
- user_flow
- design_system_element
- ui_change_request
- ui_feedback
- ui_review
- ui_observation
- ui_screenshot
- ui_state
- ui_section
- ui_page
- ui_component
- ui_render_issue
- ui_message_example
- ui_preference
- ui_context
- design_feedback
- customer_development_note
- tester_feedback
- user_feedback
- accessibility_audit
- behavior_requirement
- target_persona
- user_persona_insight
- topic
- homepage_analysis
- homepage_review_request
- feature_spec operational_entity_types:
- user_flow
- ui_change_request
- ui_review
- design_feedback
- accessibility_audit
- behavior_requirement
- design_system_element
- visual_concept
- strategy_drift_signal canonical_context_entities:
- operator_profile
accipiter
Invoke Accipiter, the UX and product design agent — user flows, information architecture, UI implementation specs, usability review. Structure and friction, not aesthetics.
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.
- today First seen · 321 lines · 0 tokens per session scan A 694593a0278b
accipiter is an agent published in the GitHub repository markmhendrickson/ateles (6 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,220 tokens. 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-09-03.
Other agents, from other repositories
content-editor
Spawn when tasks involve content editing, copy editing, proofreading, editorial quality assurance, brand voice enforcement, readability optimization, style guide compliance, content refinement, fact-checking, tone consistency, content accessibility, grammar review, content polishing, or any editorial quality…
funnel-cro-specialist
Spawn when tasks involve conversion rate optimization, CRO audits, funnel mapping, funnel analysis, landing page optimization, A/B testing, split testing, user experience for conversion, lead generation funnels, sales funnels, checkout optimization, form optimization, heatmap analysis, bounce rate reduction, or any…
omd-ui-junior
Junior UI designer that translates a journey + Core v2 design system into ASCII wireframes (Phase 4) or component manifests (Phase 6). Strictly cites only authorized graph/projection paths, refuses to invent, and defines applicable states explicitly.
explorer
gent to read and map the codebase for a specific task. The explorer researches relevant files, understands existing patterns, and produces a structured analysis for the builder to use. Invoke after the lead has defined a plan and before the builder starts. Never invoke for tasks that require writing or modifying files.
defining-agents
Agent "defining-agents" from sixb-ai/sixb, covering defining agents, config, the model, the project model catalog and instructions vs agent skills.
overview
An agent is a conversational assistant you define alongside your ontology. It calls a language model, selected worker tools, sandboxed read and bash, and an authorized Sixb API.