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 skills/oyi77/1ai-skills/code-agentnpx skills add oyi77/1ai-skills --skill code-agentgit clone --depth 1 https://github.com/oyi77/1ai-skillsWrote 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/skills/oyi77/1ai-skills/code-agent)<a href="https://agentmods.dev/skills/oyi77/1ai-skills/code-agent"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/code-agent.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 | $0.00024 | $0.00974 |
| Opus 5 | $0.00012 | $0.00487 |
| Sonnet 5 | $0.00005 | $0.00195 |
| Haiku 4.5 | $0.00002 | $0.00097 |
Grade A, and why
code-agent 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Agent
Quick Reference — see parent for full agent ecosystem.
The Code Agent converts specs and plans into working, tested code. It reads requirements or a plan JSON, produces implementation across multiple files, writes companion tests, and iterates until all verification gates pass. Its primary contract is correctness: the output must compile, pass tests, and follow project conventions.
When Not to Use
- Simple or one-off tasks — if the task is straightforward, direct execution is faster than structured methodology.
- Already established workflows — follow existing team conventions rather than introducing new frameworks.
- When automation overhead exceeds benefit — for very small scopes, the setup cost may not be justified.
Dependencies
- Python 3.8+ or Node.js 18+
- Access to relevant APIs/services for your specific use case
- Basic understanding of the domain concepts
Commands
# Refer to the skill's usage section for specific commands
# Adapt these to your workflow
Key Responsibilities
- Read specs, write code: Accept structured plans or natural-language requirements and produce production-ready implementation across the defined file boundaries
- Own the test suite: Generate unit, integration, and regression tests alongside every code change — coverage targets are non-negotiable
- Iterate on verification: Run linters, type checks, and tests after every write cycle; fix failures before declaring done
Code Example
"""Minimal code agent pattern — implement from plan."""
import json, subprocess, sys
from pathlib import Path
def implement(plan_path: str, output_dir: str) -> dict:
plan = json.loads(Path(plan_path).read_text())
changed = []
for step in plan["steps"]:
for file_spec in step.get("files", []):
# Read existing file or create new
path = Path(output_dir) / file_spec["path"]
if path.exists():
original = path.read_text()
else:
original = ""
# Apply the implementation (simplified — real agent calls an LLM)
new_code = f"# {file_spec['path']}\n# {file_spec['description']}\n{original}"
path.write_text(new_code)
changed.append(str(path))
# Write tests
for spec in plan.get("tests", []):
test_path = Path(output_dir) / spec["path"]
test_path.write_text(f"# Test for {spec['target']}\ndef test_{spec['name']}():\n assert True\n")
changed.append(str(test_path))
return {"files_changed": changed, "tests_written": len(plan.get("tests", []))}
if __name__ == "__main__":
result = implement(sys.argv[1], sys.argv[2])
print(json.dumps(result, indent=2))
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.
- 4d ago First seen · 120 lines · 24 tokens per session scan A 650ebfbcefae
code-agent is a skill published in the GitHub repository oyi77/1ai-skills (12 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 974 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 skills, from other repositories
document-query
Use when reading, extracting, summarizing, comparing, or answering questions over local or remote documents, code files, PDFs, Office files, HTML/text files, large text-heavy files, and fallback OCR for document images or scans when vision tools are unavailable or insufficient.
contribute-to-eliza
Finish and prove a scoped elizaOS GitHub issue, or independently review and repair an open elizaOS pull request. Use when contributing compute to elizaOS by selecting unclaimed work, implementing or reviewing changes, adding real tests and evidence, validating artifacts, or preparing a contribution for maintainer…
bluebubbles
Handles sending and managing iMessages through BlueBubbles, the recommended iMessage integration. Triggers when the user wants to send a text message, send an iMessage, send a text, text someone, message a contact, react with a tapback, reply to a message thread, send an attachment via iMessage, edit or unsend a sent…
nano-pdf
Edits PDF files using natural-language instructions via the nano-pdf CLI. Supports modifying text, changing titles, fixing typos, and updating content on specific pages. Use when the user wants to edit a PDF, modify PDF content, update PDF text, fix a typo in a PDF, change a PDF title, or rewrite part of a PDF page.
healthcheck
Host security hardening and risk-tolerance configuration for Otto deployments. Use when a user asks for security audits, firewall/SSH/update hardening, risk posture, exposure review, Otto cron scheduling for periodic checks, or version status checks on a machine running Otto (laptop, workstation, Pi, VPS).
things-mac
Manage Things 3 via the things CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks Otto to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.