maf-dev-loop

maf-dev-loop is a skill for Cursor from JinLee794/agent-framework-skills. It costs 70 tokens per session (3,027 once invoked), scanned A, original, MIT.

A local development and debugging guide for an AI agent, including logging, a text-based developer interface, and trace tracking. A developer interface is a screen for running and inspecting the agent during development.

In plain words
What is it for?
Use it to set up logging, run and debug agents locally, inspect traces and metrics, and diagnose agents that produce no answer.
Why use it?
It makes failures and empty responses visible instead of leaving you guessing what happened inside the agent.

Skill for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it to set up logging, run and debug agents locally, inspect traces and metrics, and diagnose agents that produce no answer.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jinlee794/agent-framework-skills/maf-dev-loop
Install

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.

Any agent
npx skills add JinLee794/agent-framework-skills --skill maf-dev-loop
Clone the repo
git clone --depth 1 https://github.com/JinLee794/agent-framework-skills

Made for: Cursor.

Wrote 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.

agentmods badge for maf-dev-loop

README.md
[![agentmods](https://agentmods.dev/badge/skills/jinlee794/agent-framework-skills/maf-dev-loop/github.svg)](https://agentmods.dev/skills/jinlee794/agent-framework-skills/maf-dev-loop)
Your own site
<a href="https://agentmods.dev/skills/jinlee794/agent-framework-skills/maf-dev-loop"><img src="https://agentmods.dev/badge/skills/jinlee794/agent-framework-skills/maf-dev-loop/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.

agentmods 80×15 button for maf-dev-loop

Your own site · 80×15
<a href="https://agentmods.dev/skills/jinlee794/agent-framework-skills/maf-dev-loop"><img src="https://agentmods.dev/badge/skills/jinlee794/agent-framework-skills/maf-dev-loop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,027 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00070 $0.03027
Opus 5.5 $0.00028 $0.01211
Sonnet 5.5 $0.00014 $0.00605
Haiku 4.5 $0.00007 $0.00303

Measured 1mo ago against content hash 9c86271ec078, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

maf-dev-loop 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.

.cursor/skills/maf-dev-loop/SKILL.md · 283 lines

How it starts

The opening of the file, as written. The whole thing — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Dev Loop — Logging, DevUI, Telemetry

Task Where
Set up logging so failures are explainable this file, below — do this first
The agent returns nothing and you cannot tell why references/diagnostics.md
Run and debug an agent locally this file, below
Voice trace attributes, metrics, full telemetry troubleshooting references/observability.md
Refresh a stale skill against the SDKs references/skill-sync.md

Logging is not optional

A voice agent fails in places nobody can see: inside a tool handler, inside an event loop, inside a config document that absorbed a misspelled key. If the seed cannot explain its own failure, it is not finished. Logging setup is scaffolding step one, not a follow-up task.

diagnostics.py

One module, no local imports, called before anything else at every entry point.

# src/<package>/diagnostics.py
import logging
import os

_NOISY = {
    "azure.identity": logging.WARNING,
    "azure.core.pipeline.policies.http_logging_policy": logging.WARNING,
    "urllib3": logging.WARNING,
}


def setup_logging() -> None:
    """Configure root logging. Must run before any module that can fail is imported."""
    level = os.getenv("LOG_LEVEL", "INFO").upper()
    logging.basicConfig(
        level=level,
        format="%(asctime)s %(levelname)-8s %(name)s %(message)s",
        force=True,  # override any handler a dependency installed at import
    )
    for name, noisy_level in _NOISY.items():
        logging.getLogger(name).setLevel(noisy_level)
    logging.getLogger("agent_framework").setLevel(level)

force=True matters: several Azure SDKs attach a handler on import, and without it basicConfig is a no-op and your format never applies.

# src/<package>/__main__.py — order is load-bearing
from dotenv import load_dotenv

from .diagnostics import setup_logging

load_dotenv()        # Agent Framework never does this for you
setup_logging()      # before any import that can fail

from .voice.runner import main   # noqa: E402 — imported after logging is live

Read the full file on GitHub · 283 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 1mo ago First seen · 283 lines · 70 tokens per session scan A 9c86271ec078

Subscribe to this mod's changes

maf-dev-loop is a skill published in the GitHub repository JinLee794/agent-framework-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 70 tokens to every session and 3,027 once invoked, about $0.0003 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-31.

Related

Other skills, from other repositories

debug-issue

Systematically debug issues using graph-powered code navigation.

thangchung/agent-engineering-experiment · 13 tokens

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

deck-retro

Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…

asheshgoplani/agent-deck · 86 tokens

incident-response-incident-response

Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.

rmyndharis/antigravity-skills · 36 tokens