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/dgunning/edgartools/taskgit clone --depth 1 https://github.com/dgunning/edgartoolsWhat 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.00013 | $0.01330 |
| Opus 5 | $0.00006 | $0.00665 |
| Sonnet 5 | $0.00003 | $0.00266 |
| Haiku 4.5 | $0.00001 | $0.00133 |
Grade A, and why
task 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 yesterday.
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:
- task — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Management Command
Create, update, and manage structured development tasks using Beads for fast, scalable tracking. This command is a wrapper around bd commands with EdgarTools-specific conventions.
Tracking System: Beads (
bdcommands) Documentation: ROADMAP.md (strategic planning), VELOCITY-TRACKING.md (historical analysis) Integration: Coordinates with product-manager for prioritization
Usage Examples
# Create a new feature task
/task new feature "Multi-company financial comparison"
# Create a bug fix task from GitHub issue
/task new bug "Cash flow statement missing values" --github=408
# List active tasks
/task list
# Show task details
/task show edgartools-abc
# Mark task as complete
/task complete edgartools-abc
Note: This command is a convenience wrapper around bd commands. For direct Beads usage:
bd create --title "Feature: X" --status open --priority P1 --labels feature
bd list --status open
bd update ISSUE_ID --status in_progress
bd update ISSUE_ID --status done
Command Implementation
This command wraps bd (Beads) commands with EdgarTools conventions:
Creating New Tasks
# Map task type to labels
case $task_type in
feature) labels="feature" ;;
bug) labels="bug" ;;
research) labels="research" ;;
refactor) labels="refactor" ;;
esac
# Create in Beads with external ref if from GitHub
if [ -n "$github_issue" ]; then
bd create --title "$task_type: $task_title" \
--status open \
--external-ref "gh:$github_issue" \
--labels "$labels" \
--priority P2
else
bd create --title "$task_type: $task_title" \
--status open \
--labels "$labels" \
--priority P2
fi
# Optionally create detailed plan markdown file for complex tasks
# (Only create if task requires architectural planning or multiple steps)
Listing Tasks
# List all open tasks
bd list --status open
# Or filter by type
bd list --status open --labels feature
bd list --status open --labels bug
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.
- yesterday First seen · 167 lines · 13 tokens per session scan A 0464838c07c5
task is a command published in the GitHub repository dgunning/edgartools (2,635 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 1,330 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.