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/martin-francois/symphony-trello/commitnpx skills add martin-francois/symphony-trello --skill commitgit clone --depth 1 https://github.com/martin-francois/symphony-trelloWrote 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/martin-francois/symphony-trello/commit)<a href="https://agentmods.dev/skills/martin-francois/symphony-trello/commit"><img src="https://agentmods.dev/badge/skills/martin-francois/symphony-trello/commit.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.1 | $0.00032 | $0.01238 |
| Opus 5 | $0.00016 | $0.00619 |
| Sonnet 5 | $0.00006 | $0.00248 |
| Haiku 4.5 | $0.00003 | $0.00124 |
Grade A, and why
commit 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.
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit
Goals
- Commit only the intended changes.
- Match the target repository's commit-message convention.
- For branches that may become GitHub pull requests, reuse a checkout-local commit author only when it was already verified or configured for this workflow. Otherwise, configure it from the authenticated GitHub login before creating commits.
- Preserve unrelated user changes.
- Include validation evidence in the commit body when it helps review.
- Reference the implemented GitHub issue in a footer when the work belongs to an issue.
Steps
-
Inspect
git status --short --branch,git diff, andgit diff --staged. -
Stage only files that belong to the current task.
-
Re-read newly added files before committing. Do not commit generated output, secrets, local run artifacts, private board names, card ids, account names, or host paths.
-
If this branch may be pushed to GitHub or published as a pull request, first check whether this checkout already has a local Git author verified by this workflow:
current_name="$(git config --local --get user.name || true)" current_email="$(git config --local --get user.email || true)" author_verified="$(git config --local --get symphony-trello.github-author-verified || true)" if [ -z "$current_name" ] || [ -z "$current_email" ] || [ "$author_verified" != "true" ]; then if ! github_name="$(gh api user --jq '.login // ""')" || [ -z "$github_name" ]; then echo "GitHub identity lookup failed: could not resolve user login" >&2 exit 1 fi if ! github_email="$(gh api user --jq '.email // ""')"; then echo "GitHub identity lookup failed: could not resolve user email metadata" >&2 exit 1 fi if [ -z "$github_email" ]; then if ! github_email="$(gh api user/emails --jq '[.[] | select(.email | endswith("@users.noreply.github.com")) | .email][0] // ""' 2>/dev/null)"; then echo "GitHub identity lookup failed: gh api user/emails needs the user:email scope; run gh auth refresh -s user:email for this account" >&2 exit 1 fi fi if [ -z "$github_email" ]; then echo "GitHub identity lookup failed: configure a public email or accessible GitHub noreply email for this account" >&2 exit 1 fi git config --local user.name "$github_name" git config --local user.email "$github_email" git config --local symphony-trello.github-author-verified true fi
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 · 121 lines · 32 tokens per session scan A 1218a8cd4b9e
commit is a skill published in the GitHub repository martin-francois/symphony-trello (2 stars, last pushed today), licensed Apache-2.0. It adds 32 tokens to every session and 1,238 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 skills, from other repositories
git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.
audit-trail
Full traceability from PRD to code commit through the CCPM spec-driven pipeline.
moai-ref-git-workflow
Git workflow patterns, branch strategies, conventional commits, and PR templates reference for git operations. Agent-extending skill that amplifies manager-git expertise with production-grade git workflow patterns. NOT for: code implementation, testing, architecture design, documentation content.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
nw-quality-framework
Quality gates - 11 commit readiness gates, build/test protocol, validation checkpoints, and quality metrics.
checkpoint-management
Git-backed state management for safe rollback. Create and restore checkpoints with tagged commits and metadata tracking.