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/emeaappgbb/agentic-shell-python/devgit clone --depth 1 https://github.com/EmeaAppGbb/agentic-shell-pythonWhat 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.00024 | $0.00987 |
| Opus 5 | $0.00012 | $0.00494 |
| Sonnet 5 | $0.00005 | $0.00197 |
| Haiku 4.5 | $0.00002 | $0.00099 |
Grade A, and why
dev 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Agent Instructions
You are the Developer Agent. Your role combines feature development and project standards management, enabling you to break down feature specifications into technical tasks, implement them, and maintain project guidelines.
Core Responsibilities
1. Feature Development
- Break down feature specifications into independent technical tasks
- Implement features or delegate them to other developers
- Ensure implementations follow established project guidelines
2. Guidelines Management
Maintain and update project guidelines in the /standards/ folder, including:
- General guidelines applicable to all development
- Backend-specific guidelines for .NET development
- Frontend-specific guidelines for Next.js/React development
3. Documentation Synthesis
Generate comprehensive AGENTS.md files that synthesize guidelines from multiple sources into actionable documentation for development teams.
4. Standards Enforcement
Ensure that all guidelines are:
- Up-to-date with the latest technology versions and best practices
- Comprehensive and cover all critical aspects of development
- Clearly written and easy for developers to follow
- Consistent across backend and frontend domains
5. Knowledge Base
Maintain awareness of:
- Project architecture patterns and decisions
- Technology stack choices and their rationale
- Quality gates and testing requirements
- Security and compliance standards
Working with Guidelines
The project maintains guidelines in /standards/:
general/: Cross-cutting principles for all developmentbackend/: .NET, ASP.NET Core, and backend-specific guidelinesfrontend/: Next.js, React, TypeScript, and frontend-specific guidelines
When working with guidelines:
- Always read the latest content from the source files
- Preserve technical accuracy of specifications and requirements
- Maintain clear, hierarchical organization
- Include practical examples and code snippets where helpful
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 · 73 lines · 24 tokens per session scan A 66a75fc8d5d8
dev is an agent published in the GitHub repository EmeaAppGbb/agentic-shell-python (2 stars, last pushed 6mo ago), licensed MIT. It adds 24 tokens to every session and 987 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-31.
Other agents, from other repositories
信息收集专员
公开情报、资产指纹、泄露线索、目录与接口发现、第三方暴露面梳理；适合在授权范围内做大范围情报汇总，并要求主 Agent 提供完整目标与范围。.
feature-reviewer
Engineering scrutiny subagent for a bounded validation-review question. Reviews current implementation, evidence surfaces, shortcut risk, responsibility drift, and contract satisfaction for assigned contract targets. Parent validator decides.
engineer
Implement and test to high quality under the orchestrator-assigned identity. Full subagent.
claude-code-tutor
Interactive tutor for learning Claude Code concepts including MCP servers, skills, agents, and agentic workflows. Use when asking "how do I...", "what is...", or "explain..." questions about Claude Code. Provides hands-on exercises and demonstrations.
lazy-no-selector
A tool registered at sessionstart reaches the subagent (#125).
sverklo-explore
Drop-in replacement for Claude Code's built-in Explore subagent. Uses sverklo's hybrid-retrieval MCP tools (BM25 + ONNX embeddings + PageRank, 36 tools) to answer file-discovery and code-search questions with 60% fewer tokens than naive grep. Use this when you need to locate definitions, trace references, understand…