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 rules/andr-ca/agentharness/agentic-loopsgit clone --depth 1 https://github.com/andr-ca/agentharnessWhat 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.00031 | $0.01913 |
| Opus 5 | $0.00015 | $0.00957 |
| Sonnet 5 | $0.00006 | $0.00383 |
| Haiku 4.5 | $0.00003 | $0.00191 |
Grade A, and why
agentic-loops 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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agentic Loops: Agents, Tools, Workflows
Structured patterns for building multi-turn agents that reason, act, and observe.
An agentic loop is:
- Think: Agent reasons about task → decides action
- Act: Call tools / take action
- Observe: Get result, update state
- Repeat: Loop until task complete
Minimal Loop — use the tested implementation, don't hand-roll this
Don't write a bespoke think/act/observe loop from scratch — it's easy to
get the tool-result protocol wrong (feeding a tool's result back as a
plain "user" message loses the call binding and looks like human input
to the model, instead of {"role": "tool", "tool_call_id": ..., ...}),
easy to leave out a budget (infinite loop if the model never stops
calling tools), and easy to skip argument validation (a malformed tool
call reaches your tool function instead of being rejected).
agent_loop.py, bundled alongside this file (a symlink back to
patterns/agentic-loops/agent_loop.py, so it resolves whether you
installed the whole harness or only this one skill), is a minimal, tested
(100% coverage), provider-neutral implementation that gets these right:
JSON-Schema-validated arguments, provider-correct tool-result messages, an
iteration + wall-clock budget, an optional approval hook, and an auditable
trace that never logs raw tool output. See
patterns/agentic-loops/README.md in the full harness checkout for the
complete usage example and what it does not cover (sandboxing,
prompt-injection handling, real cost accounting, cancellation,
retries/idempotency, persistence, evals) — that guide isn't bundled with
this skill since it's documentation, not something the skill needs to
function.
# Run from this skill's own directory, or add it to sys.path — see
# test_agent_loop.py (also bundled here) for a runnable example.
from agent_loop import Budget, ToolSpec, run_agent_loop
tool = ToolSpec(name="add", fn=add, parameters_schema={...}) # JSON Schema
result = run_agent_loop(
model_fn=my_provider_adapter, # translates to/from your provider's native shape
tools={"add": tool},
messages=[{"role": "user", "content": "What is 2 + 3?"}],
budget=Budget(max_iterations=5, max_seconds=30),
)
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 · 247 lines · 31 tokens per session scan A 0f3823977cf8
agentic-loops is a cursor rule published in the GitHub repository andr-ca/agentharness (1 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 1,913 once invoked, about $0.0002 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 cursor rules, from other repositories
prompt-routing
Route tasks to the correct Universal AI Engineering Prompt.
00-repo-context
Repo context and read order.
cursorrules
You have access to the Axis MCP tools. Use them proactively — they are your standard workflow, not optional add-ons. Never wait for the user to say "use Axis.".
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.