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/Flower7C3/tune-tanglerWrote 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/rules/flower7c3/tune-tangler/tune-tangler-project)<a href="https://agentmods.dev/rules/flower7c3/tune-tangler/tune-tangler-project"><img src="https://agentmods.dev/badge/rules/flower7c3/tune-tangler/tune-tangler-project/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/rules/flower7c3/tune-tangler/tune-tangler-project"><img src="https://agentmods.dev/badge/rules/flower7c3/tune-tangler/tune-tangler-project.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.00600 | $0.00600 |
| Opus 5 | $0.00300 | $0.00300 |
| Sonnet 5 | $0.00120 | $0.00120 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
tune-tangler-project 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 9d 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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project conventions
- Commit messages: Conventional Commits.
- Localization:
lib/l10n/*.arb, thenflutter gen-l10n. - Default branch:
main(as in this repository). - CI / release: see docs/development/WORKFLOWS.md (shared composite actions under
.github/actions/;test.ymlusesflutter-teston PR tomain(and manual dispatch);version-tag-mainon push tomainruns tests thenpubspec-bump-tag-push(pubspec+ tag); F-Droid (release-fdroid-app.yml) callspublish-fdroid-gitlab-metadatato push metadata to your fdroiddata fork (target_refoptional — empty means latest tag on the default branch); you open the fdroiddata merge request in GitLab manually;release-apk-aab-google-play.ymlrunsandroid-github-apk-aab-releaseto build signed APK/AAB from an existing tag and publish a GitHub Release — no extra commits/tags in those workflows).
Repository layout (short)
.github/workflows/— CI/CD entry workflows.github/actions/— composite actions used by workflows (e.g.setup-flutter,flutter-test)android/,ios/, … — platform projectslib/— Flutter app codedocs/— documentation (docs/development/,docs/release/,docs/features/)tools/— scripts and config (fdroid/,screenshots.sh+screenshots.json,generate-icons.sh, …)Makefile— helpers, includingpre-commithook install/remove targets.githooks/pre-commit— source for the optional local hook (copied to.git/hooks/pre-commitwhen installed).cursor/rules/— AI assistant rules (this directory)
Links
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.
- 9d ago First seen · 33 lines · 600 tokens per session scan A 1e88396cdcba
tune-tangler-project is a cursor rule published in the GitHub repository Flower7C3/tune-tangler (6 stars, last pushed 3mo ago), licensed MIT. It adds 600 tokens to every session, about $0.0030 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
compose-accessibility
Compose accessibility rules for TalkBack — icons, headings, Canvas, live regions, focus, modals, and attribute preservation.
compose-coroutines
Compose scroll/coroutine patterns — prevent programmatic scroll from being mistaken for user scroll, cancellation-safe flag resets.
testing-conventions
Testing conventions — JUnit 4, Kotest property tests, instrumented tests, what to test when.
ios-viewmodel
ViewModels conform to ObservableObject and expose state via @Published properties.
compose-ui
Compose UI conventions — Material 3, recomposition optimization, Compose-only UI, theming.
android-viewmodel
Android ViewModel conventions — StateFlow, repository abstraction, coroutines, no LiveData.