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 commands/vishnu2kmohan/mcp-server-langgraph/ci-statusgit clone --depth 1 https://github.com/vishnu2kmohan/mcp-server-langgraphWrote 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/commands/vishnu2kmohan/mcp-server-langgraph/ci-status)<a href="https://agentmods.dev/commands/vishnu2kmohan/mcp-server-langgraph/ci-status"><img src="https://agentmods.dev/badge/commands/vishnu2kmohan/mcp-server-langgraph/ci-status.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.00010 | $0.03049 |
| Opus 5 | $0.00005 | $0.01524 |
| Sonnet 5 | $0.00002 | $0.00610 |
| Haiku 4.5 | $0.00001 | $0.00305 |
Grade A, and why
ci-status 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 4d 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 — 498 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD Status
Usage: /ci-status or /ci-status --workflow <name>
Purpose: Real-time GitHub Actions workflow status and recent runs
🔄 What This Command Does
Displays current CI/CD pipeline status using GitHub CLI:
- Shows workflow run status for current branch
- Lists recent workflow runs with results
- Displays failing jobs and steps
- Shows run duration and timing
- Provides links to detailed logs
📊 Workflow Status Display
Step 1: Check GitHub CLI
Verify gh CLI is installed and authenticated:
# Check if gh is installed
if ! command -v gh &> /dev/null; then
echo "❌ GitHub CLI not installed"
echo "Install: https://cli.github.com/"
exit 1
fi
# Check authentication
if ! gh auth status &> /dev/null; then
echo "❌ Not authenticated with GitHub"
echo "Run: gh auth login"
exit 1
fi
echo "✅ GitHub CLI ready"
Step 2: Get Current Branch
Determine which branch to check:
# Get current branch
CURRENT_BRANCH=$(git rev-parse --abbrev-ref HEAD)
echo "Current branch: $CURRENT_BRANCH"
# Get latest commit
LATEST_COMMIT=$(git rev-parse --short HEAD)
echo "Latest commit: $LATEST_COMMIT"
Step 3: Fetch Workflow Runs
Get recent workflow runs for current branch:
# List recent workflow runs
gh run list \
--branch "$CURRENT_BRANCH" \
--limit 5 \
--json databaseId,displayTitle,name,status,conclusion,createdAt,updatedAt,url
# Alternative: Get runs for specific commit
gh run list \
--commit "$LATEST_COMMIT" \
--json databaseId,displayTitle,name,status,conclusion,url
Step 4: Parse Workflow Status
Extract and format workflow information:
# Parse JSON output
gh run list --branch "$CURRENT_BRANCH" --limit 5 --json name,status,conclusion,createdAt,url | \
jq -r '.[] | "\(.name)\t\(.status)\t\(.conclusion // "N/A")\t\(.createdAt)\t\(.url)"' | \
while IFS=$'\t' read -r name status conclusion created url; do
# Format status with emoji
case "$conclusion" in
success) icon="✅" ;;
failure) icon="❌" ;;
cancelled) icon="🚫" ;;
skipped) icon="⏭️ " ;;
*) icon="🔄" ;;
esac
# Format timestamp
time_ago=$(date -d "$created" +'%Y-%m-%d %H:%M')
echo "$icon $name | $status | $time_ago"
echo " $url"
done
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.
- 4d ago First seen · 498 lines · 10 tokens per session scan A 22f9e2097886
ci-status is a command published in the GitHub repository vishnu2kmohan/mcp-server-langgraph (4 stars, last pushed 11d ago), licensed MIT. It adds 10 tokens to every session and 3,049 once invoked, about $0.0001 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 commands, from other repositories
pr-check
Run all local CI checks before creating a PR.
analytics
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
environments
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
backups
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
errors
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
deployments
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.