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 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/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/skills/oyi77/1ai-skills/code-agent"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/code-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00024 | $0.01107 |
| Opus 5.5 | $0.00010 | $0.00443 |
| Sonnet 5.5 | $0.00005 | $0.00221 |
| Haiku 4.5 | $0.00002 | $0.00111 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
This agent implements features directly from specifications: it reads the requirements, writes the code, and iterates until the spec is satisfied. Use it when you have a clear written spec and want the implementation owned end-to-end. It delivers working code plus the reasoning trail behind each change.
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.
- 1mo ago Changed · +11 lines 7499a06d4b39
- 1mo 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 (17 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 1,107 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 skills, from other repositories
document-query
Read, extract or compare PDFs, Office files, URLs and large text; OCR when vision fails.
crewai-multi-agent
Multi-agent orchestration framework for autonomous AI collaboration. Use when building teams of specialized agents working together on complex tasks, when you need role-based agent collaboration with memory, or for production workflows requiring sequential/hierarchical execution. Built without LangChain dependencies…
autonomous-loops
Patterns and architectures for autonomous Claude Code loops — from simple sequential pipelines to RFC-driven multi-agent DAG systems.
ctf-misc
Provides miscellaneous CTF challenge techniques for problems that do not cleanly fit the main categories. Use for encoding puzzles, pyjails, bash jails, RF/SDR, DNS oddities, unicode tricks, esoteric languages, QR or audio puzzles, constraint solving, game theory, unusual sandbox escapes, and hybrid logic puzzles.…
backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
agent-payment-x402
Add x402 payment execution to AI agents with per-task budgets, spending controls, and non-custodial wallets. Supports Base through agentwallet-sdk and X Layer through OKX Payments / OKX Agent Payments Protocol.