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/ahmedawan-oracle/claude-code-plugins/aidp-agent-highcodenpx skills add ahmedawan-oracle/claude-code-plugins --skill aidp-agent-highcodegit clone --depth 1 https://github.com/ahmedawan-oracle/claude-code-pluginsWhat 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.00127 | $0.01653 |
| Opus 5 | $0.00063 | $0.00826 |
| Sonnet 5 | $0.00025 | $0.00331 |
| Haiku 4.5 | $0.00013 | $0.00165 |
Grade A, and why
aidp-agent-highcode 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 2d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aidp-agent-highcode — code-first AIDP agents (aidputils + LangGraph)
The GA high-code path: write a Python agent class using aidputils (pre-installed in AI Compute;
not pip-installable locally; legacy name aidp_flowutils) on top of LangGraph 1.x. You author the
.py in the workspace (aidp-workspace-files / aidp-notebooks) and run it on AI Compute. Grounded in
AIDP_High_Code_Complete_Reference.md §4–12, §22.
When to use
- "Write/code an AIDP agent", LangGraph,
create_react_agent,StateGraph, custom tool logic, multi-agent supervisor in code, or anythingaidputils. - NOT the drag-and-drop / REST node graph →
aidp-agent-flows. NOT building the RAG corpus →aidp-knowledge-bases.
Imports (current aidputils; legacy aidp_flowutils still works)
from aidputils.agents.toolkit.tool_helper import create_langgraph_tool
from aidputils.agents.toolkit.agent_helper import init_oci_llm, pre_invoke_setup
from aidputils.agents.toolkit.configs import AIDPToolConf, OCIAIConf, ModelArgs
from langgraph.prebuilt import create_react_agent
from langgraph.graph import StateGraph, MessagesState, START, END
from langchain_core.messages import HumanMessage
The agent class contract (REQUIRED)
Every agent MUST implement __init__ / setup() / async invoke():
class MyAgent:
def __init__(self) -> None:
self.agent = None # or self.graph = None
def setup(self) -> None: # sync, called once: build LLM + tools + agent
llm = init_oci_llm(OCIAIConf(
model_provider="generic", model_id="xai.grok-4",
compartment_id="ocid1.compartment.oc1..…",
endpoint="https://inference.generativeai.us-ashburn-1.oci.oraclecloud.com",
model_args=ModelArgs(temperature=0.7, max_tokens=4096),
guardrails_config={"policies": []}, auth_type="SECURITY_TOKEN", auth_profile="DEFAULT"))
tool = create_langgraph_tool(AIDPToolConf(
name="summarizer", description="Summarize text",
tool_class="PromptTool", # or "SQLTool" / "RAGTool"
conf={...}, params=[{"name":"text","type":"string","description":"…"}]).model_dump())
self.agent = create_react_agent(llm, [tool]) # single-agent; StateGraph for multi-agent
async def invoke(self, user_query: str, **kwargs):
config = pre_invoke_setup(**kwargs) # MUST be first line of every invoke
message = {"messages": [dict(HumanMessage(content=user_query))]}
return await self.agent.ainvoke(input=message, config=config)
Rules (HC ref §5): setup() is synchronous, runs once; invoke() is async, per query;
pre_invoke_setup(**kwargs) must be the first call in invoke(); input is always
{"messages": [dict(HumanMessage(content=…))]}.
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.
- 2d ago First seen · 88 lines · 127 tokens per session scan A 96c40d3dfcf8
aidp-agent-highcode is a skill published in the GitHub repository ahmedawan-oracle/claude-code-plugins (2 stars, last pushed 29d ago), licensed MIT. It adds 127 tokens to every session and 1,653 once invoked, about $0.0006 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.