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/arenukvern/mcp_flutter/skill-source-citationsnpx skills add Arenukvern/mcp_flutter --skill skill-source-citationsgit clone --depth 1 https://github.com/Arenukvern/mcp_flutterWrote 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/skills/arenukvern/mcp_flutter/skill-source-citations)<a href="https://agentmods.dev/skills/arenukvern/mcp_flutter/skill-source-citations"><img src="https://agentmods.dev/badge/skills/arenukvern/mcp_flutter/skill-source-citations.svg" alt="Measured on agentmods" 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 | $0.00057 | $0.00641 |
| Opus 5 | $0.00028 | $0.00320 |
| Sonnet 5 | $0.00011 | $0.00128 |
| Haiku 4.5 | $0.00006 | $0.00064 |
Grade A, and why
skill-source-citations 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 5d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- skill-source-citations — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill source citations
Rule: Knowledge borrowed from docs, papers, other repos, or chat research must be saved as links in the skill tree—not only in conversation.
When to use
- Creating or editing any
skills/{name}/SKILL.md - Researching harness/MCP/marketplace patterns before writing a skill
- Reviewing a PR that adds procedural claims without sources
Per-skill file (required in skill_steward)
Maintain skills/{name}/references/sources.md:
# Sources
| Topic | URL | Used for |
|-------|-----|----------|
| Agent Skills spec | https://agentskills.io/ | Frontmatter rules |
| … | … | … |
## Changelog
- 2026-05-29: initial citations
Template: citation-template.md.
Workflow (create or update skill)
- Before writing — list URLs you will rely on in
references/sources.md(can start sparse). - In SKILL.md — link to spec/docs inline where non-obvious; prefer
references/for long material. - After research — append new rows + changelog entry; never leave “we read X” only in chat.
- In PR — one line in description: “Sources updated in
references/sources.md.” - Validate —
pnpm run validatewarns ifsources.mdis missing.
What to cite
| Cite | Example |
|---|---|
| Official specs | agentskills.io, Cursor/Claude/Codex docs |
| Papers / research | SkillOpt, SkillsBench arXiv |
| Reference implementations | product MCPs, Codex plugin-eval |
| Blog/guides | Only if procedure is non-obvious; prefer primary docs |
Do not cite ephemeral chat URLs or private tokens.
Cross-skill index
Guild-wide references: docs/STANDARDS.mdx, DESIGN_FAQ.mdx.
Related skills
| Task | Skill |
|---|---|
| Scaffold skill | skill-authoring-lifecycle |
| Evaluate / improve | skill-eval-improve |
| Spec audit | skill-authoring-lifecycle |
Sources discipline (this skill)
What ships with it
2 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.
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.
- 5d ago First seen · 81 lines · 57 tokens per session scan A effe2e997841
skill-source-citations is a skill published in the GitHub repository Arenukvern/mcp_flutter (373 stars, last pushed 10d ago), licensed MIT. It adds 57 tokens to every session and 641 once invoked, about $0.0003 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-30.
Other skills, from other repositories
at_client_skills-sdk
Use this skill when a developer is building a Dart or Flutter app that depends on atclient or atclientflutter from pub.dev, stores or shares data via the Atsign Protocol, needs onboarding (CRAM new-atsign, atKeys file, keychain, APKAM) or APKAM enrollment, or asks about AtCollection , CItem , Query , sub-collections…
flutter-pre-caching
Use when preloading fonts, asset/network images, Lottie/Rive animations, local JSON/config, warming initial API data, or optimizing Flutter Web startup.
firebase-auth
Use when setting up auth, managing auth state, implementing email/password or social sign-in, handling auth errors, or managing users.
code-review
Use when asked to review a PR, MR, branch, or diff, audit changed files, or check code quality.
architecture-feature-first
Use when creating a feature, designing folder structure, adding repositories/services/view models, wiring dependency injection, or deciding which layer owns logic.
effective-dart
Use when writing Dart code, reviewing for style, refactoring naming, adding doc comments, structuring imports, or enforcing type annotations.