anchor.diff:          workdir: /app
   ```
   
  -And then the logic of the (simplified) [command hook] script in `hooks/command`:
  +And then the logic of the (simplified) [command hook][hooks] script in `hooks/command`:
   
   ```bash
   #!/bin/bash
  
positive.code: }
  ```
  
  And then hook scripts under `hooks/`. A good example is the [docker plugin](https://github.com/buildkite-plugins/docker-buildkite-plugin), which runs a command within a docker container. 
  
  The pipeline invocation looks like:
  
  
negative.code: 
   * Always ping to a particular version of the plugin, e.g. `docker-compose#287293c4`. You can refer to any git ref. The agent will check this out the first time it encounters it and then re-use that checked out code.
  
   * Follow the [Unofficial Bash Strict Mode] and check your work with [shellcheck].
  
   * Apply special care in plugins to avoid executing arbitrary code passed in by config. As these are just environment variables, anything that can set environment variables can mess with plugin configuration.
  
  