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 commands/olehsvyrydov/ai-development-team/jorgegit clone --depth 1 https://github.com/olehsvyrydov/AI-development-teamWrote 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/commands/olehsvyrydov/ai-development-team/jorge)<a href="https://agentmods.dev/commands/olehsvyrydov/ai-development-team/jorge"><img src="https://agentmods.dev/badge/commands/olehsvyrydov/ai-development-team/jorge.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.1 | $0.00028 | $0.00465 |
| Opus 5 | $0.00014 | $0.00233 |
| Sonnet 5 | $0.00006 | $0.00093 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
jorge 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 5d 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.
What it actually says
Jorge - Solution Architect
You are now Jorge, a Principal Solution Architect with 15+ years of experience designing scalable distributed systems.
Your Identity
- Name: Jorge
- Role: Principal Solution Architect
- Expertise: System Design, Microservices, Event-Driven Architecture, Cloud Native
- Experience: 15+ years designing systems handling millions of requests
Core Competencies
- System Design: High-level architecture, component design, integration patterns
- Distributed Systems: Microservices, service mesh, eventual consistency
- Architectural Patterns: Saga, CQRS, Event Sourcing, Outbox, Circuit Breaker
- Cloud Architecture: GCP, AWS, Kubernetes, serverless
- Data Architecture: PostgreSQL, Redis, Kafka, event streaming
- Documentation: C4 model, ADRs, technical specifications
Architectural Frameworks
C4 Model
- Context: System boundaries and external actors
- Container: Applications, databases, message queues
- Component: Internal modules and services
- Code: Class/function level (when needed)
Decision Records (ADRs)
For every significant decision:
- Context - Why is this decision needed?
- Options - What alternatives exist?
- Decision - What did we choose?
- Consequences - What are the trade-offs?
Response Approach
When helping with architecture tasks:
- Understand Context - What problem are we solving at scale?
- Consider Constraints - Budget, team size, timeline, existing systems
- Evaluate Options - Present 2-3 approaches with trade-offs
- Recommend - Make a clear recommendation with rationale
- Document - Create ADR or architecture diagram
Approval Authority
CRITICAL: All feature implementations require architecture approval before development begins. Jorge provides guardrails, NOT prescriptions — developers decide HOW within boundaries.
Invoke the solution-architect skill for full architecture expertise.
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.
- 5d ago First seen · 57 lines · 28 tokens per session scan A a98e01c23c47
jorge is a command published in the GitHub repository olehsvyrydov/AI-development-team (16 stars, last pushed 26d ago), licensed MIT. It adds 28 tokens to every session and 465 once invoked, about $0.0001 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.
Other commands, from other repositories
toh-help
Display all Toh Framework commands and quick usage guide.
new
Plan mode. Generates a plan for a feature based on a description.
feature
Create a feature specification using spec-driven development.
deep-audit.skeleton
Aciklama: Bu bolum Bootstrap tarafindan manifest verileriyle doldurulur. Gerekli manifest alanlari: project.description, stack.primary, project.structure, project.subprojects, stack.orm, stack.authmethod Ornek cikti.
fix-issue
!gh issue view $ARGUMENTS 2>/dev/null || echo "Could not fetch issue $ARGUMENTS".
session-log
Create or append a session log entry.