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 instructions/asisaga/linkedin.asisaga.com/azure-functionsgit clone --depth 1 https://github.com/ASISaga/linkedin.asisaga.comWrote 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/instructions/asisaga/linkedin.asisaga.com/azure-functions)<a href="https://agentmods.dev/instructions/asisaga/linkedin.asisaga.com/azure-functions"><img src="https://agentmods.dev/badge/instructions/asisaga/linkedin.asisaga.com/azure-functions.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.01077 | $0.01077 |
| Opus 5 | $0.00539 | $0.00539 |
| Sonnet 5 | $0.00215 | $0.00215 |
| Haiku 4.5 | $0.00108 | $0.00108 |
Grade A, and why
linkedin.asisaga.com azure-functions.instructions.md 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 3d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure Functions & AOS Workflow Patterns
AOSApp Setup
Every workflow module starts with a single AOSApp instance:
from aos_client import AOSApp, ObservabilityConfig
# App name comes from repository spec — see .github/specs/repository.md
app = AOSApp(
name="<app-name>",
observability=ObservabilityConfig(
structured_logging=True,
correlation_tracking=True,
health_checks=["aos", "service-bus"],
),
)
The SDK provisions HTTP triggers, Service Bus triggers, health endpoints, and auth — no boilerplate needed here.
Workflow Registration
@app.workflow("workflow-name")
async def workflow_fn(request: WorkflowRequest) -> Dict[str, Any]:
...
- Workflow names use
kebab-case - Return
{"orchestration_id": ..., "status": ...}for orchestration starters - Return plain data dicts for query/lookup workflows
Azure Functions Entry Point
# function_app.py — zero boilerplate
from <package>.workflows import app
functions = app.get_functions()
Never add Azure Functions decorators directly to function_app.py.
Orchestration Patterns
Perpetual orchestration (most workflows)
status = await request.client.start_orchestration(
agent_ids=agent_ids,
purpose="Describe the ongoing goal",
purpose_scope="Scope of responsibility",
context=request.body,
)
return {"orchestration_id": status.orchestration_id, "status": status.status.value}
Sequential workflow
status = await request.client.start_orchestration(
...,
workflow="sequential",
)
Hierarchical workflow
status = await request.client.start_orchestration(
...,
workflow="hierarchical",
)
Advanced: OrchestrationRequest with MCP servers
from aos_client import MCPServerConfig, OrchestrationPurpose, OrchestrationRequest
req = OrchestrationRequest(
agent_ids=agent_ids,
purpose=OrchestrationPurpose(purpose=..., purpose_scope=...),
context=request.body,
mcp_servers={agent_id: [MCPServerConfig(server_name="erp")]},
)
status = await request.client.submit_orchestration(req)
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.
- 3d ago First seen · 161 lines · 1,077 tokens per session scan A 29e5702269c5
linkedin.asisaga.com azure-functions.instructions.md is an instructions file published in the GitHub repository ASISaga/linkedin.asisaga.com (0 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 1,077 tokens to every session, about $0.0054 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 instructions, from other repositories
dstack AGENTS.md
AGENTS.md instructions for dstackai/dstack, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
apm python.instructions.md
Python development guidelines.
AppClaw CLAUDE.md
Claude Code instructions for appclawhq/AppClaw, covering claude.md, what is appclaw?, build & run commands, architecture and entry point & cli modes (src/index.ts).
streamlit e2e_playwright.instructions.md
Instructions for streamlit/streamlit, covering streamlit e2e tests, test structure, key fixtures and utilities, external test mode and url handling (no localhost hardcoding).
awsmux AGENTS.md
Instructions for 0hardik1/awsmux, covering agents.md, what awsmux is, build, test, verify, layout and the safety model — invariants you must not weaken.
claude-tui AGENTS.md
AGENTS.md instructions for slima4/claude-tui, covering agents.md, quick commands, testing, gotchas (hard-won knowledge) and local development.