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/indexgit 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.01441 |
| Opus 5 | $0.00000 | $0.00720 |
| Sonnet 5 | $0.00000 | $0.00288 |
| Haiku 4.5 | $0.00000 | $0.00144 |
Grade A, and why
index 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.
How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent is a reusable, typed Junjo executable for the case where a model
chooses the next capability at runtime. It is a sibling of Workflow. An
Agent has no fabricated Graph, and a Tool is an operation rather than a Node.
The definition declares all behavior-affecting structure up front:
- a stable application-owned key and display name;
- exact instructions and typed input/output boundaries;
- one provider-neutral
ModelDriverBinding; - an ordered collection of explicitly typed
Tooldefinitions; - positive model-request and Tool-call limits.
Every execute call creates a fresh run identity, private Store, transcript,
counters, usage aggregate, lifecycle snapshot, and per-run collaborator cache.
The caller owns request dependencies, history selection, persistence, provider
credentials, transactions, and product transport.
Minimal definition
The core package deliberately owns no provider SDK. A ModelDriver translates
one immutable normalized ModelRequest into either FinalOutputResponse
or ToolCallsResponse.
from pydantic import BaseModel
from junjo import (
Agent,
AgentLimits,
ModelDriverBinding,
ModelDriverDescriptor,
)
from junjo.agent import FinalOutputResponse
from junjo.agent.testing import ScriptedModelDriver
class Question(BaseModel):
text: str
class Answer(BaseModel):
text: str
driver = ScriptedModelDriver([
FinalOutputResponse(output={"text": "deterministic answer"})
])
agent = Agent(
key="answer_question",
name="Answer Question",
instructions="Answer using available evidence.",
input_type=Question,
model=ModelDriverBinding.shared(
descriptor=ModelDriverDescriptor(
driver_key="scripted",
provider="junjo",
model="scripted-v1",
fixture=True,
),
driver=driver,
),
tools=[],
output_type=Answer,
limits=AgentLimits(model_requests=4, tool_calls=8),
)
result = await agent.execute(
Question(text="What happened?"),
dependencies=None,
)
The successful result always contains validated output, a detached normalized
transcript, usage evidence, identities, counters, and terminal reason. Failure
raises a typed AgentError; there is no output-less success result.
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 · 162 lines · 0 tokens per session scan A 6671b24bf3c0
index 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 1,441 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.