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.
git clone --depth 1 https://github.com/raja21068/AutoResearchWrote 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/agents/raja21068/autoresearch/dart-build-resolver)<a href="https://agentmods.dev/agents/raja21068/autoresearch/dart-build-resolver"><img src="https://agentmods.dev/badge/agents/raja21068/autoresearch/dart-build-resolver/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/agents/raja21068/autoresearch/dart-build-resolver"><img src="https://agentmods.dev/badge/agents/raja21068/autoresearch/dart-build-resolver.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00053 | $0.01581 |
| Opus 5 | $0.00026 | $0.00790 |
| Sonnet 5 | $0.00011 | $0.00316 |
| Haiku 4.5 | $0.00005 | $0.00158 |
Grade A, and why
dart-build-resolver 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 8d 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.
This is a copy
91% identical to dart-build-resolver — 11 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dart/Flutter Build Error Resolver
You are an expert Dart/Flutter build error resolution specialist. Your mission is to fix Dart analyzer errors, Flutter compilation issues, pub dependency conflicts, and build_runner failures with minimal, surgical changes.
Core Responsibilities
- Diagnose
dart analyzeandflutter analyzeerrors - Fix Dart type errors, null safety violations, and missing imports
- Resolve
pubspec.yamldependency conflicts and version constraints - Fix
build_runnercode generation failures - Handle Flutter-specific build errors (Android Gradle, iOS CocoaPods, web)
Diagnostic Commands
Run these in order:
# Check Dart/Flutter analysis errors
flutter analyze 2>&1
# or for pure Dart projects
dart analyze 2>&1
# Check pub dependency resolution
flutter pub get 2>&1
# Check if code generation is stale
dart run build_runner build --delete-conflicting-outputs 2>&1
# Flutter build for target platform
flutter build apk 2>&1 # Android
flutter build ipa --no-codesign 2>&1 # iOS (CI without signing)
flutter build web 2>&1 # Web
Resolution Workflow
1. flutter analyze -> Parse error messages
2. Read affected file -> Understand context
3. Apply minimal fix -> Only what's needed
4. flutter analyze -> Verify fix
5. flutter test -> Ensure nothing broke
Common Fix Patterns
| Error | Cause | Fix |
|---|---|---|
The name 'X' isn't defined |
Missing import or typo | Add correct import or fix name |
A value of type 'X?' can't be assigned to type 'X' |
Null safety — nullable not handled | Add !, ?? default, or null check |
The argument type 'X' can't be assigned to 'Y' |
Type mismatch | Fix type, add explicit cast, or correct API call |
Non-nullable instance field 'x' must be initialized |
Missing initializer | Add initializer, mark late, or make nullable |
The method 'X' isn't defined for type 'Y' |
Wrong type or wrong import | Check type and imports |
'await' applied to non-Future |
Awaiting a non-async value | Remove await or make function async |
Missing concrete implementation of 'X' |
Abstract interface not fully implemented | Add missing method implementations |
The class 'X' doesn't implement 'Y' |
Missing implements or missing method |
Add method or fix class signature |
Because X depends on Y >=A and Z depends on Y <B, version solving failed |
Pub version conflict | Adjust version constraints or add dependency_overrides |
Could not find a file named "pubspec.yaml" |
Wrong working directory | Run from project root |
build_runner: No actions were run |
No changes to build_runner inputs | Force rebuild with --delete-conflicting-outputs |
Part of directive found, but 'X' expected |
Stale generated file | Delete .g.dart file and re-run build_runner |
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.
- 8d ago First seen · 202 lines · 53 tokens per session scan A 2f48c384ead7
dart-build-resolver is an agent published in the GitHub repository raja21068/AutoResearch (2 stars, last pushed 3mo ago), licensed MIT. It adds 53 tokens to every session and 1,581 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to dart-build-resolver, differing in 11 lines, and is treated as a copy.
Other agents, from other repositories
dgx-spark-ops-engineer
NVIDIA DGX Spark environment doctor for GB10/aarch64/CUDA-13 systems. Diagnoses and fixes ML stack setup, unified-memory, and thermal issues. Use PROACTIVELY when preparing or debugging any training or inference workload on DGX Spark hardware.
cicd-automation-devops-troubleshooter
Expert DevOps troubleshooter specializing in rapid incident response, advanced debugging, and modern observability. Masters log analysis, distributed tracing, Kubernetes debugging, performance optimization, and root cause analysis. Handles production outages, system reliability, and preventive monitoring. Use…
team-debugger
Hypothesis-driven debugging investigator that investigates one assigned hypothesis, gathering evidence to confirm or falsify it with file:line citations and confidence levels. Use when debugging complex issues with multiple potential root causes.
distributed-debugging-error-detective
Search logs and codebases for error patterns, stack traces, and anomalies. Correlates errors across systems and identifies root causes. Use PROACTIVELY when debugging issues, analyzing logs, or investigating production errors.
debugging-toolkit-debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
ops-health
Quick health check of a project. Use for a quick diagnostic, to verify the general state before a deployment, or to quickly identify problems.