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/mdrideout/junjo/compositiongit clone --depth 1 https://github.com/mdrideout/junjoWhat 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.00387 |
| Opus 5 | $0.00000 | $0.00193 |
| Sonnet 5 | $0.00000 | $0.00077 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
composition 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.
What it actually says
Composition uses ordinary application boundaries. Junjo does not add a generic Agent Node, Workflow Tool, shared Store mapper, or universal executable base.
Workflow to Agent
An application Node reads a detached Workflow Store snapshot, maps it to Agent
input and dependencies, awaits Agent.execute(), then maps the detached
result through explicit Store actions. The Agent span is a physical and
semantic child of the Node. Agent state is never the Workflow Store.
Agent to Workflow
An application Tool service maps its validated input into a fresh Workflow
definition, awaits the normal Workflow API, and maps ExecutionResult into
the Tool output type. The hierarchy is Agent -> Tool operation -> Workflow.
The Workflow retains its own Graph, Store, identities, limits, lifecycle, and
result; the Agent is its semantic parent executable.
Failure and cancellation
An uncaught Agent error fails its Node and Workflow. The caller receives a
WorkflowExecutionError with the Agent error retained as its cause. An
uncaught admitted Workflow failure inside a Tool likewise retains its typed
Workflow boundary error and original domain cause beneath AgentToolError.
Cancellation propagates through every active owner and operation;
WorkflowCancelledError remains an asyncio.CancelledError while adding
the admitted Workflow run identity. Parent and child limits are independent,
and completed side effects are not rolled back.
Application code may explicitly catch a known typed failure and commit a domain recovery result. Junjo does not supply an implicit fallback, transaction, compensation, or persistent memory policy.
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.
- yesterday First seen · 38 lines · 0 tokens per session scan A 6dccf3fb891d
composition is an agent published in the GitHub repository mdrideout/junjo (20 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 387 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-08-30.
Other agents, from other repositories
dynamic-agents
Dynamic agents use functions instead of static values for instructions, model, and tools. These functions receive runtime context and return the appropriate configuration for each operation.
openai-sdk
OpenAI's Agents SDK supports structured tool use and multi-modal workflows. ContextForge can serve as a unified tool registry for OpenAI agents.
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
loom-senior-software-engineer
Use PROACTIVELY for architecture design, complex debugging, design patterns, code review, test strategy, data modeling, ML system design, UX strategy, documentation architecture, and strategic technical decisions across all domains.