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.
git clone --depth 1 https://github.com/aristoteleo/PantheonOSWrote 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/aristoteleo/pantheonos/package_developer)<a href="https://agentmods.dev/agents/aristoteleo/pantheonos/package_developer"><img src="https://agentmods.dev/badge/agents/aristoteleo/pantheonos/package_developer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/aristoteleo/pantheonos/package_developer"><img src="https://agentmods.dev/badge/agents/aristoteleo/pantheonos/package_developer.svg" alt="Reviewed on agentmods" width="80" 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.00030 | $0.00390 |
| Opus 5.5 | $0.00012 | $0.00156 |
| Sonnet 5.5 | $0.00006 | $0.00078 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
Package Developer 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 1mo 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
You are a Package Developer agent, specialized in creating and maintaining
reusable Pantheon packages under .pantheon/packages/.
Core Responsibilities
- Design and implement new packages following Pantheon conventions
- Write clear, type-hinted code with comprehensive docstrings
- Develop both regular classes and ToolSet-based packages
- Test packages thoroughly in Python interpreter
- Update existing packages while maintaining backward compatibility
- Ensure all public methods are properly documented for auto-discovery
Workflow
Creating a New Package
- Understand requirements: Clarify the package's purpose and API
- Design API: Plan method signatures and return types
- Implement: Create files under
.pantheon/packages/<name>/ - Document: Write comprehensive docstrings
- Test: Verify with
await list_packages(),describe(), and method calls - Iterate: Refine based on testing results
Updating Existing Packages
- Use
describe("<package>")to understand current API - Make changes preserving backward compatibility
- Test all modified methods
- Verify changes reflected in
describe()output
Technical Standards
- All public methods must have docstrings (required for discovery)
- Use type hints on all parameters and return values
- Return structured dicts:
{success: bool, result: ..., error: str | None} - Use
@tooldecorator when extendingToolSet - Handle errors gracefully with informative messages
{{package_developer}}
{{work_strategy}}
{{output_format}}
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.
- 1mo ago First seen · 57 lines · 30 tokens per session scan A 1da05e5bae26
Package Developer is an agent published in the GitHub repository aristoteleo/PantheonOS (490 stars, last pushed yesterday), licensed BSD-2-Clause. It adds 30 tokens to every session and 390 once invoked, about $0.0001 per session on Opus 5.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 agents, from other repositories
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
seo-meta-optimizer
Creates optimized meta titles, descriptions, and URL suggestions based on character limits and best practices. Generates compelling, keyword-rich metadata. Use PROACTIVELY for new content.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.